FLUSH TABLES FOR EXPORT
Syntax
FLUSH TABLES table_name [, table_name] FOR EXPORT
Contents
Description
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 Archive, Aria, CSV, InnoDB, MyISAM and MERGE tables.
The table is read locked until one has issued UNLOCK TABLES.
If a storage engine does not support FLUSH TABLES FOR EXPORT
, a 1031 error (SQLSTATE '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
- Any statement trying to update any table
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
LOCK TABLES ... WRITE
FLUSH FOR EXPORT
is not written to the binary log.
This statement requires the RELOAD and the LOCK TABLES 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:
ERROR 1146 (42S02): Table 'test.xxx' doesn't exist
If a table is a view, an error like the following will be produced:
ERROR 1347 (HY000): 'test.v' is not BASE TABLE
Example
FLUSH TABLES test.t1 FOR EXPORT; # Copy files related to the table (see below) UNLOCK TABLES;
For a full description, please see copying MariaDB tables.
See Also
- Copying Tables Between Different MariaDB Databases and MariaDB Servers
- Copying Transportable InnoDB Tablespaces
- myisampack - Compressing the MyISAM data file for easier distribution.
- aria_pack - Compressing the Aria data file for easier distribution