--bind-address

On a computer having multiple network interfaces, use this option to select which interface to use for connecting to the MySQLserver.

--compress

Compress all information sent between the client and the server if possible. See Section 4.2.6, “Connection Compression Control”.As of MySQL 8.0.18, this option is deprecated. It will be removed in a future MySQL version. See the section called “LegacyConnection Compression Configuration”.

--default-auth

A hint about which client-side authentication plugin to use. See Section 6.2.17, “Pluggable Authentication”.

--enable-cleartext-plugin

Enable the mysql_clear_password cleartext authentication plugin. (See Section 6.4.1.4, “Client-Side Cleartext PluggableAuthentication”.)

--get-server-public-key

Request from the server the public key required for RSA key pair-based password exchange. This option applies to clients thatauthenticate with the caching_sha2_password authentication plugin. For that plugin, the server does not send the public keyunless requested. This option is ignored for accounts that do not authenticate with that plugin. It is also ignored if RSA-basedpassword exchange is not used, as is the case when the client connects to the server using a secure connection.If --server-public-key-path=file_name is given and specifies a valid public key file, it takes precedence over

--get-server-public-key.

For information about the caching_sha2_password plugin, see Section 6.4.1.3, “Caching SHA-2 Pluggable Authentication”.

--host

Dump data from the MySQL server on the given host. The default host is localhost.

--login-path

Read options from the named login path in the .mylogin.cnf login path file. A “login path” is an option group containing optionsthat specify which MySQL server to connect to and which account to authenticate as. To create or modify a login path file, usethe mysql_config_editor utility. See mysql_config_editor(1).For additional information about this and other option-file options, see Section 4.2.2.3, “Command-Line Options that AffectOption-File Handling”.

--password[

The password of the MySQL account used for connecting to the server. The password value is optional. If not given, mysqldumpprompts for one. If given, there must be no space between --password= or -p and the password following it. If no password optionis specified, the default is to send no password.Specifying a password on the command line should be considered insecure. To avoid giving the password on the command line, use anoption file. See Section 6.1.2.1, “End-User Guidelines for Password Security”.To explicitly specify that there is no password and that mysqldump should not prompt for one, use the --skip-password option.

--pipe

On Windows, connect to the server using a named pipe. This option applies only if the server was started with the named_pipesystem variable enabled to support named-pipe connections. In addition, the user making the connection must be a member of theWindows group specified by the named_pipe_full_access_group system variable.

--plugin-dir

The directory in which to look for plugins. Specify this option if the --default-auth option is used to specify an authenticationplugin but mysqldump does not find it. See Section 6.2.17, “Pluggable Authentication”.

--port

For TCP/IP connections, the port number to use.

--protocol

The connection protocol to use for connecting to the server. It is useful when the other connection parameters normally result inuse of a protocol other than the one you want. For details on the permissible values, see Section 4.2.4, “Connecting to the MySQLServer Using Command Options”.

--secure-auth

This option was removed in MySQL 8.0.3.

--server-public-key-path

The path name to a file containing a client-side copy of the public key required by the server for RSA key pair-based passwordexchange. The file must be in PEM format. This option applies to clients that authenticate with the sha256_password orcaching_sha2_password authentication plugin. This option is ignored for accounts that do not authenticate with one of thoseplugins. It is also ignored if RSA-based password exchange is not used, as is the case when the client connects to the serverusing a secure connection.If --server-public-key-path=file_name is given and specifies a valid public key file, it takes precedence over

--socket

For connections to localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.On Windows, this option applies only if the server was started with the named_pipe system variable enabled to support named-pipeconnections. In addition, the user making the connection must be a member of the Windows group specified by thenamed_pipe_full_access_group system variable.

--ssl*

Options that begin with --ssl specify whether to connect to the server using SSL and indicate where to find SSL keys andcertificates. See the section called “Command Options for Encrypted Connections”.

--tls-ciphersuites

The permissible ciphersuites for encrypted connections that use TLSv1.3. The value is a list of one or more colon-separatedciphersuite names. The ciphersuites that can be named for this option depend on the SSL library used to compile MySQL. Fordetails, see Section 6.3.2, “Encrypted Connection TLS Protocols and Ciphers”.This option was added in MySQL 8.0.16.

--tls-version

The permissible TLS protocols for encrypted connections. The value is a list of one or more comma-separated protocol names. Theprotocols that can be named for this option depend on the SSL library used to compile MySQL. For details, see Section 6.3.2,“Encrypted Connection TLS Protocols and Ciphers”.

--user

The user name of the MySQL account to use for connecting to the server.

--defaults-extra-file

Read this option file after the global option file but (on Unix) before the user option file. If the file does not exist or isotherwise inaccessible, an error occurs. file_name is interpreted relative to the current directory if given as a relative pathname rather than a full path name.For additional information about this and other option-file options, see Section 4.2.2.3, “Command-Line Options that AffectOption-File Handling”.

--defaults-file

Use only the given option file. If the file does not exist or is otherwise inaccessible, an error occurs. file_name isinterpreted relative to the current directory if given as a relative path name rather than a full path name.Exception: Even with --defaults-file, client programs read .mylogin.cnf.For additional information about this and other option-file options, see Section 4.2.2.3, “Command-Line Options that AffectOption-File Handling”.

--defaults-group-suffix

Read not only the usual option groups, but also groups with the usual names and a suffix of str. For example, mysqldump normallyreads the [client] and [mysqldump] groups. If the --defaults-group-suffix=_other option is given, mysqldump also reads the[client_other] and [mysqldump_other] groups.For additional information about this and other option-file options, see Section 4.2.2.3, “Command-Line Options that AffectOption-File Handling”.

--no-defaults

Do not read any option files. If program startup fails due to reading unknown options from an option file, --no-defaults can beused to prevent them from being read.The exception is that the .mylogin.cnf file, if it exists, is read in all cases. This permits passwords to be specified in asafer way than on the command line even when --no-defaults is used. (.mylogin.cnf is created by the mysql_config_editor utility.See mysql_config_editor(1).)For additional information about this and other option-file options, see Section 4.2.2.3, “Command-Line Options that AffectOption-File Handling”.

--print-defaults

Print the program name and all options that it gets from option files.For additional information about this and other option-file options, see Section 4.2.2.3, “Command-Line Options that AffectOption-File Handling”.DDL Options.PP Usage scenarios for mysqldump include setting up an entire new MySQL instance (including database tables), andreplacing data inside an existing instance with existing databases and tables. The following options let you specify which things totear down and set up when restoring a dump, by encoding various DDL statements within the dump file.

--add-drop-database

Write a DROP DATABASE statement before each CREATE DATABASE statement. This option is typically used in conjunction with the

--all-databases

or --databases option because no CREATE DATABASE statements are written unless one of those options is specified.

--add-drop-table

Write a DROP TABLE statement before each CREATE TABLE statement.

--add-drop-trigger

Write a DROP TRIGGER statement before each CREATE TRIGGER statement.

--all-tablespaces

Adds to a table dump all SQL statements needed to create any tablespaces used by an NDB table. This information is not otherwiseincluded in the output from mysqldump. This option is currently relevant only to NDB Cluster tables.

--no-create-db

Suppress the CREATE DATABASE statements that are otherwise included in the output if the --databases or --all-databases option isgiven.

--no-create-info

Do not write CREATE TABLE statements that create each dumped table.NoteThis option does not exclude statements creating log file groups or tablespaces from mysqldump output; however, you can usethe --no-tablespaces option for this purpose.

--no-tablespaces

This option suppresses all CREATE LOGFILE GROUP and CREATE TABLESPACE statements in the output of mysqldump.

--replace

Write REPLACE statements rather than INSERT statements.Debug Options.PP The following options print debugging information, encode debugging information in the dump file, or let the dumpoperation proceed regardless of potential problems.

--allow-keywords

Permit creation of column names that are keywords. This works by prefixing each column name with the table name.

--comments

Write additional information in the dump file such as program version, server version, and host. This option is enabled bydefault. To suppress this additional information, use --skip-comments.

--debug[

Write a debugging log. A typical debug_options string is d:t:o,file_name. The default value is d:t:o,/tmp/mysqldump.trace.

--debug-check

Print some debugging information when the program exits.

--debug-info

Print debugging information and memory and CPU usage statistics when the program exits.

--dump-date

If the --comments option is given, mysqldump produces a comment at the end of the dump of the following form:

--

However, the date causes dump files taken at different times to appear to be different, even if the data are otherwise identical.

--force

Ignore all errors; continue even if an SQL error occurs during a table dump.One use for this option is to cause mysqldump to continue executing even when it encounters a view that has become invalidbecause the definition refers to a table that has been dropped. Without --force, mysqldump exits with an error message. With

--log-error

Log warnings and errors by appending them to the named file. The default is to do no logging.

--skip-comments

See the description for the --comments option.

--verbose

Verbose mode. Print more information about what the program does.Help Options.PP The following options display information about the mysqldump command itself.

--help

Display a help message and exit.

--version

Display version information and exit.Internationalization Options.PP The following options change how the mysqldump command represents character data with nationallanguage settings.

--character-sets-dir

The directory where character sets are installed. See Section 10.15, “Character Set Configuration”.

--default-character-set

Use charset_name as the default character set. See Section 10.15, “Character Set Configuration”. If no character set isspecified, mysqldump uses utf8.

--no-set-names

Turns off the --set-charset setting, the same as specifying --skip-set-charset.

--set-charset

Write SET NAMES default_character_set to the output. This option is enabled by default. To suppress the SET NAMES statement, use

--skip-set-charset.

Replication Options.PP The mysqldump command is frequently used to create an empty instance, or an instance including data, on aslave server in a replication configuration. The following options apply to dumping and restoring data on replication master andslave servers.

--apply-slave-statements

For a slave dump produced with the --dump-slave option, add a STOP SLAVE statement before the CHANGE MASTER TO statement and aSTART SLAVE statement at the end of the output.

--delete-master-logs

On a master replication server, delete the binary logs by sending a PURGE BINARY LOGS statement to the server after performingthe dump operation. This option automatically enables --master-data.

--dump-slave[

This option is similar to --master-data except that it is used to dump a replication slave server to produce a dump file that canbe used to set up another server as a slave that has the same master as the dumped server. It causes the dump output to include aCHANGE MASTER TO statement that indicates the binary log coordinates (file name and position) of the dumped slave's master. TheCHANGE MASTER TO statement reads the values of Relay_Master_Log_File and Exec_Master_Log_Pos from the SHOW SLAVE STATUS outputand uses them for MASTER_LOG_FILE and MASTER_LOG_POS respectively. These are the master server coordinates from which the slaveshould start replicating.NoteInconsistencies in the sequence of transactions from the relay log which have been executed can cause the wrong position tobe used. See Section 17.4.1.33, “Replication and Transaction Inconsistencies” for more information.

--dump-slave

causes the coordinates from the master to be used rather than those of the dumped server, as is done by the

--master-data

This option causes mysqldump to stop the slave SQL thread before the dump and restart it again after.In conjunction with --dump-slave, the --apply-slave-statements and --include-master-host-port options can also be used.

--include-master-host-port

For the CHANGE MASTER TO statement in a slave dump produced with the --dump-slave option, add MASTER_HOST and MASTER_PORT optionsfor the host name and TCP/IP port number of the slave's master.

--master-data[

Use this option to dump a master replication server to produce a dump file that can be used to set up another server as a slaveof the master. It causes the dump output to include a CHANGE MASTER TO statement that indicates the binary log coordinates (filename and position) of the dumped server. These are the master server coordinates from which the slave should start replicatingafter you load the dump file into the slave.If the option value is 2, the CHANGE MASTER TO statement is written as an SQL comment, and thus is informative only; it has noeffect when the dump file is reloaded. If the option value is 1, the statement is not written as a comment and takes effect whenthe dump file is reloaded. If no option value is specified, the default value is 1.This option requires the RELOAD privilege and the binary log must be enabled.The --master-data option automatically turns off --lock-tables. It also turns on --lock-all-tables, unless --single-transactionalso is specified, in which case, a global read lock is acquired only for a short time at the beginning of the dump (see thedescription for --single-transaction). In all cases, any action on logs happens at the exact moment of the dump.It is also possible to set up a slave by dumping an existing slave of the master, using the --dump-slave option, which overrides

--set-gtid-purged

This option is for servers that use GTID-based replication (gtid_mode=ON). It controls the inclusion of a SET@@GLOBAL.gtid_purged statement in the dump output, which updates the value of gtid_purged on a server where the dump file isreloaded, to add the GTID set from the source server's gtid_executed system variable. gtid_purged holds the GTIDs of alltransactions that have been applied on the server, but do not exist on any binary log file on the server. mysqldump thereforeadds the GTIDs for the transactions that were executed on the source server, so that the target server records these transactionsas applied, although it does not have them in its binary logs. --set-gtid-purged also controls the inclusion of a SET@@SESSION.sql_log_bin=0 statement, which disables binary logging while the dump file is being reloaded. This statement preventsnew GTIDs from being generated and assigned to the transactions in the dump file as they are executed, so that the original GTIDsfor the transactions are used.If you do not set the --set-gtid-purged option, the default is that a SET @@GLOBAL.gtid_purged statement is included in the dumpoutput if GTIDs are enabled on the server you are backing up, and the set of GTIDs in the global value of the gtid_executedsystem variable is not empty. A SET @@SESSION.sql_log_bin=0 statement is also included if GTIDs are enabled on the server.In MySQL 5.6 and 5.7, you can replace the value of gtid_purged with a specified GTID set, provided that gtid_executed andgtid_purged are empty. From MySQL 8.0, you can either replace the value of gtid_purged with a specified GTID set, or you can adda plus sign (+) to the statement to append a specified GTID set to the GTID set that is already held by gtid_purged. mysqldump'sSET @@GLOBAL.gtid_purged statement includes a plus sign (+) in a version comment that takes effect when the dump file is replayedon releases from MySQL 8.0, meaning that for these releases, the GTID set from the dump file is added to the existing gtid_purgedvalue. For MySQL 5.6 and 5.7, the value of gtid_purged is replaced with the GTID set from the dump file, which can only happenwhen gtid_executed is the empty set (so when replication has not been started previously, or when replication was not previouslyusing GTIDs). For the exact details of how the SET @@GLOBAL.gtid_purged statement operates, see the gtid_purged description forthe release where the dump file is to be replayed.It is important to note that the value that is included by mysqldump for the SET @@GLOBAL.gtid_purged statement includes theGTIDs of all transactions in the gtid_executed set on the server, even those that changed suppressed parts of the database, orother databases on the server that were not included in a partial dump. This can mean that after the gtid_purged value has beenupdated on the server where the dump file is replayed, GTIDs are present that do not relate to any data on the target server. Ifyou do not replay any further dump files on the target server, the extraneous GTIDs do not cause any problems with the futureoperation of the server, but they make it harder to compare or reconcile GTID sets on different servers in the replicationtopology. If you do replay a further dump file on the target server that contains the same GTIDs (for example, another partialdump from the same origin server), any SET @@GLOBAL.gtid_purged statement in the second dump file fails. In this case, eitherremove the statement manually before replaying the dump file, or output the dump file without the statement.NoteFor MySQL 5.6 and 5.7, it is not recommended to load a dump file when GTIDs are enabled on the server (gtid_mode=ON), if yourdump file includes system tables. mysqldump issues DML instructions for the system tables which use the non-transactionalMyISAM storage engine, and this combination is not permitted when GTIDs are enabled.If the SET @@GLOBAL.gtid_purged statement would not have the desired result on your target server, you can exclude the statementfrom the output, or (from MySQL 8.0.17) include it but comment it out so that it is not actioned automatically. You can alsoinclude the statement but manually edit it in the dump file to achieve the desired result.The possible values for the --set-gtid-purged option are as follows:AUTOThe default value. If GTIDs are enabled on the server you are backing up and gtid_executed is not empty, SET@@GLOBAL.gtid_purged is added to the output, containing the GTID set from gtid_executed. If GTIDs are enabled, SET@@SESSION.sql_log_bin=0 is added to the output. If GTIDs are not enabled on the server, the statements are not added to theoutput.OFFSET @@GLOBAL.gtid_purged is not added to the output, and SET @@SESSION.sql_log_bin=0 is not added to the output. For a serverwhere GTIDs are not in use, use this option or AUTO. Only use this option for a server where GTIDs are in use if you are surethat the required GTID set is already present in gtid_purged on the target server and should not be changed, or if you planto identify and add any missing GTIDs manually.ONIf GTIDs are enabled on the server you are backing up, SET @@GLOBAL.gtid_purged is added to the output (unless gtid_executedis empty), and SET @@SESSION.sql_log_bin=0 is added to the output. An error occurs if you set this option but GTIDs are notenabled on the server. For a server where GTIDs are in use, use this option or AUTO, unless you are sure that the GTIDs ingtid_executed are not needed on the target server.COMMENTEDAvailable from MySQL 8.0.17. If GTIDs are enabled on the server you are backing up, SET @@GLOBAL.gtid_purged is added to theoutput (unless gtid_executed is empty), but it is commented out. This means that the value of gtid_executed is available inthe output, but no action is taken automatically when the dump file is reloaded. SET @@SESSION.sql_log_bin=0 is added to theoutput, and it is not commented out. With COMMENTED, you can control the use of the gtid_executed set manually or throughautomation. For example, you might prefer to do this if you are migrating data to another server that already has differentactive databases.Format Options.PP The following options specify how to represent the entire dump file or certain kinds of data in the dump file. Theyalso control whether certain optional information is written to the dump file.

--compact

Produce more compact output. This option enables the --skip-add-drop-table, --skip-add-locks, --skip-comments,

--skip-disable-keys

and --skip-set-charset options.

--compatible

Produce output that is more compatible with other database systems or with older MySQL servers. The only permitted value for thisoption is ansi, which has the same meaning as the corresponding option for setting the server SQL mode. See Section 5.1.11,“Server SQL Modes”.

--complete-insert

Use complete INSERT statements that include column names.

--create-options

Include all MySQL-specific table options in the CREATE TABLE statements.

--fields-terminated-by

These options are used with the --tab option and have the same meaning as the corresponding FIELDS clauses for LOAD DATA. SeeSection 13.2.7, “LOAD DATA Syntax”.

--hex-blob

Dump binary columns using hexadecimal notation (for example, 'abc' becomes 0x616263). The affected data types are BINARY,VARBINARY, BLOB types, BIT, all spatial data types, and other non-binary data types when used with the binary character set.

--lines-terminated-by

This option is used with the --tab option and has the same meaning as the corresponding LINES clause for LOAD DATA. SeeSection 13.2.7, “LOAD DATA Syntax”.

--quote-names

Quote identifiers (such as database, table, and column names) within ` characters. If the ANSI_QUOTES SQL mode is enabled,identifiers are quoted within " characters. This option is enabled by default. It can be disabled with --skip-quote-names, butthis option should be given after any option such as --compatible that may enable --quote-names.

--result-file

Direct output to the named file. The result file is created and its previous contents overwritten, even if an error occurs whilegenerating the dump.This option should be used on Windows to prevent newline \n characters from being converted to \r\n carriage return/newlinesequences.

--tab

Produce tab-separated text-format data files. For each dumped table, mysqldump creates a tbl_name.sql file that contains theCREATE TABLE statement that creates the table, and the server writes a tbl_name.txt file that contains its data. The option valueis the directory in which to write the files.NoteThis option should be used only when mysqldump is run on the same machine as the mysqld server. Because the server creates*.txt files in the directory that you specify, the directory must be writable by the server and the MySQL account that youuse must have the FILE privilege. Because mysqldump creates *.sql in the same directory, it must be writable by your systemlogin account.By default, the .txt data files are formatted using tab characters between column values and a newline at the end of each line.The format can be specified explicitly using the --fields-xxx and --lines-terminated-by options.Column values are converted to the character set specified by the --default-character-set option.

--tz-utc

This option enables TIMESTAMP columns to be dumped and reloaded between servers in different time zones. mysqldump sets itsconnection time zone to UTC and adds SET TIME_ZONE='+00:00' to the dump file. Without this option, TIMESTAMP columns are dumpedand reloaded in the time zones local to the source and destination servers, which can cause the values to change if the serversare in different time zones. --tz-utc also protects against changes due to daylight saving time. --tz-utc is enabled bydefault. To disable it, use --skip-tz-utc.

--xml

Write dump output as well-formed XML.NULL, 'NULL', and Empty Values: For a column named column_name, the NULL value, an empty string, and the string value 'NULL' aredistinguished from one another in the output generated by this option as follows.┌─────────────────────┬───────────────────────────────────────────────┐│Value: │ XML Representation: │├─────────────────────┼───────────────────────────────────────────────┤│NULL (unknown value) │ ││ │ <field name="column_name" ││ │ xsi:nil="true" /> │├─────────────────────┼───────────────────────────────────────────────┤│ │ ││ │ <field name="column_name"></field> │├─────────────────────┼───────────────────────────────────────────────┤│ │ ││ │ <field ││ │ name="column_name">NULL</field> │└─────────────────────┴───────────────────────────────────────────────┘The output from the mysql client when run using the --xml option also follows the preceding rules. (See the section called “MYSQLCLIENT OPTIONS”.)XML output from mysqldump includes the XML namespace, as shown here:shell> mysqldump --xml -u root world City<?xml version="1.0"?><mysqldump xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><database name="world"><table_structure name="City"><field Field="ID" Type="int(11)" Null="NO" Key="PRI" Extra="auto_increment" /><field Field="Name" Type="char(35)" Null="NO" Key="" Default="" Extra="" /><field Field="CountryCode" Type="char(3)" Null="NO" Key="" Default="" Extra="" /><field Field="District" Type="char(20)" Null="NO" Key="" Default="" Extra="" /><field Field="Population" Type="int(11)" Null="NO" Key="" Default="0" Extra="" /><key Table="City" Non_unique="0" Key_name="PRIMARY" Seq_in_index="1" Column_name="ID"Collation="A" Cardinality="4079" Null="" Index_type="BTREE" Comment="" /><options Name="City" Engine="MyISAM" Version="10" Row_format="Fixed" Rows="4079"Avg_row_length="67" Data_length="273293" Max_data_length="18858823439613951"Index_length="43008" Data_free="0" Auto_increment="4080"Create_time="2007-03-31 01:47:01" Update_time="2007-03-31 01:47:02"Collation="latin1_swedish_ci" Create_options="" Comment="" /></table_structure><table_data name="City"><row><field name="ID">1</field><field name="Name">Kabul</field><field name="CountryCode">AFG</field><field name="District">Kabol</field><field name="Population">1780000</field></row>...<row><field name="ID">4079</field><field name="Name">Rafah</field><field name="CountryCode">PSE</field><field name="District">Rafah</field><field name="Population">92020</field></row></table_data></database></mysqldump>Filtering Options.PP The following options control which kinds of schema objects are written to the dump file: by category, such astriggers or events; by name, for example, choosing which databases and tables to dump; or even filtering rows from the table datausing a WHERE clause.

--databases

Dump several databases. Normally, mysqldump treats the first name argument on the command line as a database name and followingnames as table names. With this option, it treats all name arguments as database names. CREATE DATABASE and USE statements areincluded in the output before each new database.This option may be used to dump the performance_schema database, which normally is not dumped even with the --all-databasesoption. (Also use the --skip-lock-tables option.)

--events

Include Event Scheduler events for the dumped databases in the output. This option requires the EVENT privileges for thosedatabases.The output generated by using --events contains CREATE EVENT statements to create the events.

--ignore-error

Ignore the specified errors. The option value is a list of comma-separated error numbers specifying the errors to ignore duringmysqldump execution. If the --force option is also given to ignore all errors, --force takes precedence.

--ignore-table

Do not dump the given table, which must be specified using both the database and table names. To ignore multiple tables, use thisoption multiple times. This option also can be used to ignore views.

--no-data

Do not write any table row information (that is, do not dump table contents). This is useful if you want to dump only the CREATETABLE statement for the table (for example, to create an empty copy of the table by loading the dump file).

--routines

Include stored routines (procedures and functions) for the dumped databases in the output. This option requires the global SELECTprivilege.The output generated by using --routines contains CREATE PROCEDURE and CREATE FUNCTION statements to create the routines.

--tables

Override the --databases or -B option. mysqldump regards all name arguments following the option as table names.

--triggers

Include triggers for each dumped table in the output. This option is enabled by default; disable it with --skip-triggers.To be able to dump a table's triggers, you must have the TRIGGER privilege for the table.Multiple triggers are permitted. mysqldump dumps triggers in activation order so that when the dump file is reloaded, triggersare created in the same activation order. However, if a mysqldump dump file contains multiple triggers for a table that have thesame trigger event and action time, an error occurs for attempts to load the dump file into an older server that does not supportmultiple triggers. (For a workaround, see Downgrade Notes[1]; you can convert triggers to be compatible with older servers.)

--where

Dump only rows selected by the given WHERE condition. Quotes around the condition are mandatory if it contains spaces or othercharacters that are special to your command interpreter.Examples:

-w"userid<1"

Performance Options.PP The following options are the most relevant for the performance particularly of the restore operations. Forlarge data sets, restore operation (processing the INSERT statements in the dump file) is the most time-consuming part. When it isurgent to restore data quickly, plan and test the performance of this stage in advance. For restore times measured in hours, youmight prefer an alternative backup and restore solution, such as MySQL Enterprise Backup for InnoDB-only and mixed-use databases.Performance is also affected by the transactional options, primarily for the dump operation.

--disable-keys

For each table, surround the INSERT statements with /*!40000 ALTER TABLE tbl_name DISABLE KEYS */; and /*!40000 ALTER TABLEtbl_name ENABLE KEYS */; statements. This makes loading the dump file faster because the indexes are created after all rows areinserted. This option is effective only for nonunique indexes of MyISAM tables.

--extended-insert

Write INSERT statements using multiple-row syntax that includes several VALUES lists. This results in a smaller dump file andspeeds up inserts when the file is reloaded.

--insert-ignore

Write INSERT IGNORE statements rather than INSERT statements.

--network-timeout

Enable large tables to be dumped by setting --max-allowed-packet to its maximum value and network read and write timeouts to alarge value. This option is enabled by default. To disable it, use --skip-network-timeout.

--opt

This option, enabled by default, is shorthand for the combination of --add-drop-table --add-locks --create-options --disable-keys

--quick

This option is useful for dumping large tables. It forces mysqldump to retrieve rows for a table from the server a row at a timerather than retrieving the entire row set and buffering it in memory before writing it out.

--skip-opt

See the description for the --opt option.Transactional Options.PP The following options trade off the performance of the dump operation, against the reliability andconsistency of the exported data.

--add-locks

Surround each table dump with LOCK TABLES and UNLOCK TABLES statements. This results in faster inserts when the dump file isreloaded. See Section 8.2.5.1, “Optimizing INSERT Statements”.

--flush-logs

Flush the MySQL server log files before starting the dump. This option requires the RELOAD privilege. If you use this option incombination with the --all-databases option, the logs are flushed for each database dumped. The exception is when using

--lock-all-tables

moment that all tables are locked by FLUSH TABLES WITH READ LOCK. If you want your dump and the log flush to happen at exactlythe same moment, you should use --flush-logs together with --lock-all-tables, --master-data, or --single-transaction.

--flush-privileges

Add a FLUSH PRIVILEGES statement to the dump output after dumping the mysql database. This option should be used any time thedump contains the mysql database and any other database that depends on the data in the mysql database for proper restoration.NoteFor upgrades to MySQL 5.7.2 or higher from older versions, do not use --flush-privileges. For upgrade instructions in thiscase, see Section 2.11.4, “Changes in MySQL 8.0”.

--lock-tables

For each dumped database, lock all tables to be dumped before dumping them. The tables are locked with READ LOCAL to permitconcurrent inserts in the case of MyISAM tables. For transactional tables such as InnoDB, --single-transaction is a much betteroption than --lock-tables because it does not need to lock the tables at all.Because --lock-tables locks tables for each database separately, this option does not guarantee that the tables in the dump fileare logically consistent between databases. Tables in different databases may be dumped in completely different states.Some options, such as --opt, automatically enable --lock-tables. If you want to override this, use --skip-lock-tables at the endof the option list.

--no-autocommit

Enclose the INSERT statements for each dumped table within SET autocommit = 0 and COMMIT statements.

--order-by-primary

Dump each table's rows sorted by its primary key, or by its first unique index, if such an index exists. This is useful whendumping a MyISAM table to be loaded into an InnoDB table, but makes the dump operation take considerably longer.

--shared-memory-base-name

On Windows, the shared-memory name to use for connections made using shared memory to a local server. The default value is MYSQL.The shared-memory name is case-sensitive.This option applies only if the server was started with the shared_memory system variable enabled to support shared-memoryconnections.

--single-transaction

This option sets the transaction isolation mode to REPEATABLE READ and sends a START TRANSACTION SQL statement to the serverbefore dumping data. It is useful only with transactional tables such as InnoDB, because then it dumps the consistent state ofthe 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 MyISAMor 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. Aconsistent read is not isolated from those statements, so use of them on a table to be dumped can cause the SELECT that isperformed by mysqldump to retrieve the table contents to obtain incorrect contents or fail.The --single-transaction option and the --lock-tables option are mutually exclusive because LOCK TABLES causes any pendingtransactions to be committed implicitly.To dump large tables, combine the --single-transaction option with the --quick option.Option Groups· The --opt option turns on several settings that work together to perform a fast dump operation. All of these settings are on bydefault, because --opt is on by default. Thus you rarely if ever specify --opt. Instead, you can turn these settings off as agroup by specifying --skip-opt, the optionally re-enable certain settings by specifying the associated options later on thecommand line.· The --compact option turns off several settings that control whether optional statements and comments appear in the output.Again, you can follow this option with other options that re-enable certain settings, or turn all the settings on by using the

--skip-compact

When you selectively enable or disable the effect of a group option, order is important because options are processed first to last.For example, --disable-keys --lock-tables --skip-opt would not have the intended effect; it is the same as --skip-opt by itself.Examples.PP To make a backup of an entire database:shell> mysqldump db_name > backup-file.sqlTo load the dump file back into the server:shell> mysql db_name < backup-file.sqlAnother way to reload the dump file:shell> mysql -e "source /path-to-backup/backup-file.sql" db_namemysqldump is also very useful for populating databases by copying data from one MySQL server to another:shell> mysqldump --opt db_name | mysql --host=remote_host -C db_nameYou can dump several databases with one command:shell> mysqldump --databases db_name1 [db_name2 ...] > my_databases.sqlTo dump all databases, use the --all-databases option:shell> mysqldump --all-databases > all_databases.sqlFor InnoDB tables, mysqldump provides a way of making an online backup:shell> mysqldump --all-databases --master-data --single-transaction > all_databases.sqlThis backup acquires a global read lock on all tables (using FLUSH TABLES WITH READ LOCK) at the beginning of the dump. As soon asthis lock has been acquired, the binary log coordinates are read and the lock is released. If long updating statements are runningwhen the FLUSH statement is issued, the MySQL server may get stalled until those statements finish. After that, the dump becomes lockfree and does not disturb reads and writes on the tables. If the update statements that the MySQL server receives are short (in termsof execution time), the initial lock period should not be noticeable, even with many updates.For point-in-time recovery (also known as “roll-forward,” when you need to restore an old backup and replay the changes that happenedsince that backup), it is often useful to rotate the binary log (see Section 5.4.4, “The Binary Log”) or at least know the binary logcoordinates to which the dump corresponds:shell> mysqldump --all-databases --master-data=2 > all_databases.sqlOr:shell> mysqldump --all-databases --flush-logs --master-data=2> all_databases.sqlThe --master-data and --single-transaction options can be used simultaneously, which provides a convenient way to make an onlinebackup suitable for use prior to point-in-time recovery if tables are stored using the InnoDB storage engine.For more information on making backups, see Section 7.2, “Database Backup Methods”, and Section 7.3, “Example Backup and RecoveryStrategy”.· To select the effect of --opt except for some features, use the --skip option for each feature. To disable extended inserts andmemory buffering, use --opt --skip-extended-insert --skip-quick. (Actually, --skip-extended-insert --skip-quick is sufficientbecause --opt is on by default.)· To reverse --opt for all features except index disabling and table locking, use --skip-opt --disable-keys --lock-tables.Restrictions.PP mysqldump does not dump the performance_schema or sys schema by default. To dump any of these, name them explicitlyon the command line. You can also name them with the --databases option. For performance_schema, also use the --skip-lock-tablesoption.mysqldump does not dump the INFORMATION_SCHEMA schema.mysqldump does not dump InnoDB CREATE TABLESPACE statements.mysqldump does not dump the NDB Cluster ndbinfo information database.mysqldump includes statements to recreate the general_log and slow_query_log tables for dumps of the mysql database. Log tablecontents are not dumped.If you encounter problems backing up views due to insufficient privileges, see Section 24.9, “Restrictions on Views” for aworkaround.COPYRIGHTCopyright © 1997, 2019, Oracle and/or its affiliates. All rights reserved.This documentation is free software; you can redistribute it and/or modify it only under the terms of the GNU General Public Licenseas published by the Free Software Foundation; version 2 of the License.This documentation is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty ofMERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.You should have received a copy of the GNU General Public License along with the program; if not, write to the Free SoftwareFoundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA or see http://www.gnu.org/licenses/.NOTES1. Downgrade Noteshttps://dev.mysql.com/doc/refman/5.7/en/downgrading-to-previous-series.html