content_image/748716.jpg
This option is enabled by default. To disable it and suppress the SET NAMES  statement, use --skip- set-charset . 

• --set-gtid-purged= value 

This option enables control over global transaction ID (GTID) information written to the dump file, by indicating whether to add a SET @@GLOBAL.gtid_purged  statement to the output. This option may also cause a statement to be written to the output that disables binary logging while the dump file is being reloaded. 

<img src='content_image/748716.jpg'>

The --set-gtid-purged  option has the following effect on binary logging when the dump file is reloaded: 

• --set-gtid-purged=OFF : SET @@SESSION.SQL_LOG_BIN=0;  is not added to the output. 

• --set-gtid-purged=ON : SET @@SESSION.SQL_LOG_BIN=0;  is added to the output. 

• --set-gtid-purged=AUTO : SET @@SESSION.SQL_LOG_BIN=0;  is added to the output if GTIDs are enabled on the server you are backing up (that is, if AUTO  evaluates to ON ). 

• --single-transaction 

This option sets the transaction isolation mode to REPEATABLE READ  and sends a START TRANSACTION  SQL statement to the server before dumping data. It is useful only with transactional tables such as InnoDB , because then it dumps the consistent state of the database at the time when START TRANSACTION  was issued without blocking any applications. 

When using this option, you should keep in mind that only InnoDB  tables are dumped in a consistent state. For example, any MyISAM  or MEMORY  tables dumped while using this option may still change state. 

While a --single-transaction  dump is in process, to ensure a valid dump file (correct table contents and binary log coordinates), no other connection should use the following statements: ALTER TABLE , CREATE TABLE , DROP TABLE , RENAME TABLE , TRUNCATE TABLE . A consistent read is not isolated from those statements, so use of them on a table to be dumped can cause the SELECT  that is performed by mysqlpump  to retrieve the table contents to obtain incorrect contents or fail. 

--add-locks  and --single-transaction  are mutually exclusive. 

• --skip-definer 

Omit DEFINER  and SQL SECURITY  clauses from the CREATE  statements for views and stored programs. The dump file, when reloaded, creates objects that use the default DEFINER  and SQL SECURITY  values. See Section 25.6, “Stored Object Access Control” . 

• --skip-dump-rows , -d 

