Description:
Implement an interface between the storage engine and the user terminal via the MySQL command, allowing the user to manage the 'check-point' of the database through commands, drawing an analogy to "Oracle" with the appeal: "BEGIN BACKUP", but different from the existing resource today "FLUSH tABLE fOR EXPORT xxx" because this feature carries lock on the table.
How to repeat:
Appeal to the Administrator manage the 'check-point' of the database, otherwise it will be much easier to manage the use of 'EXPORT' using some command like 'BACKUP WITH FLUSH LOGS' or making an analogy to the oracle 'BEGIN BACKUP' thus the DBMS do the 'Check point' of transactional logs and would no longer apply the pending transactions in the transactional log datafiles, waiting for a command to release the administrator, this feature would be useful for implementing backups and other maintenance processes in datafiles, disk, etc.
Suggested fix:
Implement an interface between the storage engine and the user terminal via the MySQL command, allowing the user to manage the 'check-point' of the database through commands, drawing an analogy to "Oracle" with the appeal: "BEGIN BACKUP", but different from the existing resource today "FLUSH tABLE fOR EXPORT xxx" because this feature carries lock on the table.
The user would run the command: (FLUSH LOGS WITH BACKUP UNDO)
This command is for the sequence of check-points and waiting for the next instruction from the user to release, it would be with the following command: (UNDO FLUSH LOGS)
