Prepare individual tables for binary backup. This command flushes changes to disk and locks tables, allowing safe copying of .ibd files while the server runs.
FLUSH TABLES ... FOR EXPORT flushes changes to the specified tables to disk so that binary copies can be made while the server is still running. This works for , , , , and tables.
The table is read locked until you issue .
If a storage engine does not support FLUSH TABLES FOR EXPORT, a 1031 error ( 'HY000') is produced.
If FLUSH TABLES ... FOR EXPORT is in effect in the session, the following statements will produce an error if attempted:
FLUSH TABLES WITH READ LOCK
FLUSH TABLES ... WITH READ LOCK
FLUSH TABLES ... FOR EXPORT
If any of the following statements is in effect in the session, attempting FLUSH TABLES ... FOR EXPORT will produce an error.
FLUSH TABLES ... WITH READ LOCK
FLUSH TABLES ... FOR EXPORT
LOCK TABLES ... READ
FLUSH FOR EXPORT is not written to the .
This statement requires the and the privileges.
If one of the specified tables cannot be locked, none of the tables will be locked.
If a table does not exist, an error like the following will be produced:
If a table is a view, an error like the following will be produced:
For a full description, please see .
- Compressing the MyISAM data file for easier distribution.
This page is licensed: CC BY-SA / Gnu FDL
FLUSH TABLE[S] table_name [, table_name] FOR EXPORTLOCK TABLES ... WRITEaria_pack - Compressing the Aria data file for easier distribution
ERROR 1146 (42S02): Table 'test.xxx' doesn't existERROR 1347 (HY000): 'test.v' is not BASE TABLEFLUSH TABLES test.t1 FOR EXPORT;
# Copy files related to the table (see below)
UNLOCK TABLES;