CodePudding user response:

You are so not to reply to perform again that time of SQL

After another row pattern to recover data

CodePudding user response:

There are two ways to get the binlog recovery
Before deleting a there is a perfect, binlog contains from perfect to remove in time before all the logs, this kind of circumstance is to restore complete, application of biolog to the front of the delete time points, the problem is caused by the reduction time points after all the operations is missing, so generally is to build a new instance, on the new instance this way to find the data you need and go back to the real server

2 kinds of the cenotaph is undo, need binlog to ROW mode, so just have data completely, and then through the mysqlbilog - v - base64 - output=decode - rows scripts generate data operation, find the DELETE, will DELETE rewritten to INSERT, and then can be performed on the server, the operation complexity is higher, but can realize accurate restore

CodePudding user response:

Upstairs is the solution, not the row level binlog, my understanding is only restore deleted all the data before operation, then find out the related data,