mysqldump — A Database Backup Program This option is useful for dumping large tables. It forces  mysqldump  to retrieve rows for a table from the server a row at a time rather than retrieving the entire row set and buffering it in memory before writing it out. See the description for the  --opt  option. • --skip-opt • --add-locks • --flush-logs ,  -F Transactional Options The following options trade off the performance of the dump operation, against the reliability and consistency of the exported data. Surround each table dump with  LOCK TABLES  and  UNLOCK TABLES  statements. This results in faster inserts when the dump file is reloaded. See Section 8.2.5.1, “Optimizing INSERT Statements” . Flush the MySQL server log files before starting the dump. This option requires the  RELOAD  privilege. If you use this option in combination with the  --all-databases  option, the logs are flushed  for each database dumped . The exception is when using  --lock-all-tables ,  --master-data , or  -- single-transaction : In this case, the logs are flushed only once, corresponding to the moment that all tables are locked by  FLUSH TABLES WITH READ LOCK . If you want your dump and the log flush to happen at exactly the same moment, you should use  --flush-logs  together with  --lock-all- tables ,  --master-data , or  --single-transaction . Add a  FLUSH PRIVILEGES  statement to the dump output after dumping the  mysql  database. This option should be used any time the dump contains the  mysql  database and any other database that depends on the data in the  mysql  database for proper restoration. Because the dump file contains a  FLUSH PRIVILEGES  statement, reloading the file requires privileges sufficient to execute that statement. • --flush-privileges Note For upgrades to MySQL 5.7 or higher from older versions, do not use  -- flush-privileges . For upgrade instructions in this case, see Section 2.11.4, “Changes in MySQL 8.0” . Lock all tables across all databases. This is achieved by acquiring a global read lock for the duration of the whole dump. This option automatically turns off  --single-transaction  and  --lock-tables . For each dumped database, lock all tables to be dumped before dumping them. The tables are locked with  READ LOCAL  to permit concurrent inserts in the case of  MyISAM  tables. For transactional tables such as  InnoDB ,  --single-transaction  is a much better option than  --lock-tables  because it does not need to lock the tables at all. • --lock-all-tables ,  -x • --lock-tables ,  -l 498