性能和可扩展性注意事项Performance and Scalability Considerations

调用语法Invocation Syntax

选项语法 - 按字母顺序排列的摘要Option Syntax - Alphabetical Summary

连接选项Connection Options

选项文件选项Option-File Options

DDL 选项DDL Options

调试选项Debug Options

帮助选项Help Options

国际化选项Internationalization Options

复制选项Replication Options

格式选项Format Options

过滤选项Filtering Options

性能选项Performance Options

事务选项Transactional Options

选项组Option Groups

示例Examples

限制Restrictions

--bind-address=ip_address

在具有多个网络接口的计算机上，使用此选项选择用于连接到 MySQL 服务器的接口。On a computer having multiple network interfaces, use this option to select which interface to use for connecting to the MySQL server.

--compress, -C

如果可能，压缩客户端与服务器之间发送的所有信息。参见 第 6.2.8 节，“连接压缩控制”。Compress all information sent between the client and the server if possible. See Section 6.2.8, “Connection Compression Control”.

此选项已被弃用。预计将在 MySQL 的未来版本中移除。请参阅 配置遗留连接压缩。This option is deprecated. Expect it to be removed in a future version of MySQL. See Configuring Legacy Connection Compression.

--compression-algorithms=value --compression-algorithms=value

允许用于与服务器连接的压缩算法。可用算法与 protocol_compression_algorithms 系统变量的算法相同。默认值为 uncompressed。The permitted compression algorithms for connections to the server. The available algorithms are the same as for the protocol_compression_algorithms system variable. The default value is uncompressed.

更多信息，请参阅 第 6.2.8 节，“连接压缩控制”。For more information, see Section 6.2.8, “Connection Compression Control”.

--default-auth=plugin --default-auth=plugin

关于使用哪种客户端身份验证插件的提示。请参见 第 8.2.17 节，“可插拔身份验证”。A hint about which client-side authentication plugin to use. See Section 8.2.17, “Pluggable Authentication”.

--enable-cleartext-plugin

启用 mysql_clear_password 明文身份验证插件。（参见 第 8.4.1.4 节，“客户端明文可插拔身份验证”。）Enable the mysql_clear_password cleartext authentication plugin. (See Section 8.4.1.4, “Client-Side Cleartext Pluggable Authentication”.)

--get-server-public-key

向服务器请求用于基于 RSA 密钥对的密码交换所需的公钥。此选项适用于使用 caching_sha2_password 身份验证插件进行身份验证的客户端。对于该插件，服务器不会发送公钥，除非被请求。对于未使用该插件进行身份验证的账户，此选项将被忽略。当未使用基于 RSA 的密码交换时（例如客户端使用安全连接连接服务器时），此选项也将被忽略。Request from the server the public key required for RSA key pair-based password exchange. This option applies to clients that authenticate with the caching_sha2_password authentication plugin. For that plugin, the server does not send the public key unless requested. This option is ignored for accounts that do not authenticate with that plugin. It is also ignored if RSA-based password exchange is not used, as is the case when the client connects to the server using a secure connection.

如果--server-public-key-path=file_name 已给出并指定有效的公钥文件，它优先于 --get-server-public-key。If --server-public-key-path=file_name is given and specifies a valid public key file, it takes precedence over --get-server-public-key.

有关 caching_sha2_password 插件的信息，请参见 第 8.4.1.2 节，“缓存 SHA-2 可插拔认证”。For information about the caching_sha2_password plugin, see Section 8.4.1.2, “Caching SHA-2 Pluggable Authentication”.

--host=host_name, -h host_name --host=host_name, -h host_name

从给定的 MySQL 服务器转储数据主机。默认主机为 localhost。Dump data from the MySQL server on the given host. The default host is localhost.

--login-path=name --login-path=name

从名为登录路径的 .mylogin.cnf 登录路径文件中读取选项。“登录路径” 是一个选项组，包含指定要连接哪个 MySQL 服务器以及以哪个帐户进行身份验证的选项。要创建或修改登录路径文件，请使用 mysql_config_editor 工具。参见 第 6.6.7 节，“mysql_config_editor — MySQL 配置工具”。Read options from the named login path in the .mylogin.cnf login path file. A “login path” is an option group containing options that specify which MySQL server to connect to and which account to authenticate as. To create or modify a login path file, use the mysql_config_editor utility. See Section 6.6.7, “mysql_config_editor — MySQL Configuration Utility”.

有关此选项文件选项及其他选项文件选项的更多信息，请参见 第 6.2.2.3 节，“影响选项文件处理的命令行选项”。For additional information about this and other option-file options, see Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”.

--no-login-paths

跳过从登录路径文件读取选项。Skips reading options from the login path file.

相关内容参见--login-path信息。See --login-path for related information.

有关此选项文件选项及其他选项文件选项的更多信息，请参见 第 6.2.2.3 节，“影响选项文件处理的命令行选项”。For additional information about this and other option-file options, see Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”.

--password[=password]，-p[password] --password[=password], -p[password]

用于连接服务器的 MySQL 帐户的密码。密码值是可选的。如果未给出，mysqldump 会提示输入一个。如果给出，--password= 或 -p 与其后面的密码之间必须没有空格。如果未指定密码选项，则默认不发送密码。The password of the MySQL account used for connecting to the server. The password value is optional. If not given, mysqldump prompts for one. If given, there must be no space between --password= or -p and the password following it. If no password option is specified, the default is to send no password.

在命令行中指定密码应被视为不安全。为了避免在命令行中输入密码，请使用选项文件。请参阅 第 8.1.2.1 节，“终端用户密码安全指南”。Specifying a password on the command line should be considered insecure. To avoid giving the password on the command line, use an option file. See Section 8.1.2.1, “End-User Guidelines for Password Security”.

要显式指定没有密码并且mysqldump 不应提示输入密码，请使用--skip-password 选项。To explicitly specify that there is no password and that mysqldump should not prompt for one, use the --skip-password option.

--password1[=pass_val]

多重身份验证因素的密码 1 用于连接服务器的 MySQL 帐户。密码值是可选的。如果未给出，mysqldump 会提示输入一个。如果给出，--password1= 与其后面的密码之间必须没有空格。如果未指定密码选项，则默认不发送密码。The password for multifactor authentication factor 1 of the MySQL account used for connecting to the server. The password value is optional. If not given, mysqldump prompts for one. If given, there must be no space between --password1= and the password following it. If no password option is specified, the default is to send no password.

在命令行中指定密码应被视为不安全。为了避免在命令行中输入密码，请使用选项文件。请参阅 第 8.1.2.1 节，“终端用户密码安全指南”。Specifying a password on the command line should be considered insecure. To avoid giving the password on the command line, use an option file. See Section 8.1.2.1, “End-User Guidelines for Password Security”.

要显式指定没有密码并且mysqldump 不应提示输入密码，请使用--skip-password1 选项。To explicitly specify that there is no password and that mysqldump should not prompt for one, use the --skip-password1 option.

--password1 和 --password 是同义词，--skip-password1 和 --skip-password。--password1 and --password are synonymous, as are --skip-password1 and --skip-password.

--password2[=pass_val]

用于连接服务器的 MySQL 帐户的多重身份验证因子 2 的密码。该选项的语义类似于 --password1 的语义；有关详细信息，请参阅该选项的说明。The password for multifactor authentication factor 2 of the MySQL account used for connecting to the server. The semantics of this option are similar to the semantics for --password1; see the description of that option for details.

--password3[=pass_val]

用于连接的 MySQL 帐户的多重身份验证因子 3 的密码服务器。该选项的语义类似于 --password1 的语义；有关详细信息，请参阅该选项的说明。The password for multifactor authentication factor 3 of the MySQL account used for connecting to the server. The semantics of this option are similar to the semantics for --password1; see the description of that option for details.

--pipe, -W

在 Windows 上，通过命名管道连接到服务器。此选项仅在服务器启动时已启用 named_pipe 系统变量以支持命名管道连接的情况下适用。此外，进行连接的用户必须是由 named_pipe_full_access_group 系统变量指定的 Windows 组的成员。On Windows, connect to the server using a named pipe. This option applies only if the server was started with the named_pipe system variable enabled to support named-pipe connections. In addition, the user making the connection must be a member of the Windows group specified by the named_pipe_full_access_group system variable.

--plugin-authentication-kerberos-client-mode=value --plugin-authentication-kerberos-client-mode=value

在 Windows 上，authentication_kerberos_client 身份验证插件支持此插件选项。它提供了客户端用户可以在运行时设置的两个可能值：SSPI 和 GSSAPI。On Windows, the authentication_kerberos_client authentication plugin supports this plugin option. It provides two possible values that the client user can set at runtime: SSPI and GSSAPI.

客户端插件选项的默认值使用安全支持提供程序接口 (SSPI)，该接口能够从 Windows 内存缓存中获取凭据。或者，客户端用户可以通过 Windows 上的 MIT Kerberos 库选择支持通用安全服务应用程序接口 (GSSAPI) 的模式。 GSSAPI 能够获取之前使用 kinit 命令生成的缓存凭据。The default value for the client-side plugin option uses Security Support Provider Interface (SSPI), which is capable of acquiring credentials from the Windows in-memory cache. Alternatively, the client user can select a mode that supports Generic Security Service Application Program Interface (GSSAPI) through the MIT Kerberos library on Windows. GSSAPI is capable of acquiring cached credentials previously generated by using the kinit command.

有关详细信息，请参阅GSSAPI 模式下 Windows 客户端的命令。For more information, see Commands for Windows Clients in GSSAPI Mode.

--plugin-dir=dir_name --plugin-dir=dir_name

查找插件的目录。如果使用 --default-auth 选项指定身份验证插件，但 mysqldump 找不到它，请指定此选项。请参阅第 8.2.17 节“可插入身份验证”。The directory in which to look for plugins. Specify this option if the --default-auth option is used to specify an authentication plugin but mysqldump does not find it. See Section 8.2.17, “Pluggable Authentication”.

--port=port_num，-P port_num --port=port_num, -P port_num

对于 TCP/IP 连接，要使用的端口号。For TCP/IP connections, the port number to use.

--protocol={TCP|SOCKET|PIPE|MEMORY}

用于连接服务器的传输协议。当其他连接参数通常导致使用的协议不是您想要的协议时，这很有用。有关允许值的详细信息，请参阅第 6.2.7 节，“连接传输协议”。The transport protocol to use for connecting to the server. It is useful when the other connection parameters normally result in use of a protocol other than the one you want. For details on the permissible values, see Section 6.2.7, “Connection Transport Protocols”.

--server-public-key-path=file_name --server-public-key-path=file_name

包含服务器所需的 RSA 密钥对密码交换的客户端副本公钥的 PEM 格式文件的路径名。此选项适用于使用 sha256_password（已弃用）或 caching_sha2_password 身份验证插件进行身份验证的客户端。对于不使用这些插件之一进行身份验证的帐户，将忽略此选项。如果未使用基于 RSA 的密码交换（例如客户端使用安全连接连接到服务器的情况），此选项也将被忽略。The path name to a file in PEM format containing a client-side copy of the public key required by the server for RSA key pair-based password exchange. This option applies to clients that authenticate with the sha256_password (deprecated) or caching_sha2_password authentication plugin. This option is ignored for accounts that do not authenticate with one of those plugins. It is also ignored if RSA-based password exchange is not used, as is the case when the client connects to the server using a secure connection.

如果--server-public-key-path=file_name 已给出并指定有效的公钥文件，它优先于 --get-server-public-key。If --server-public-key-path=file_name is given and specifies a valid public key file, it takes precedence over --get-server-public-key.

对于 sha256_password（已弃用），此选项仅在 MySQL 使用 OpenSSL 构建时才适用。For sha256_password (deprecated), this option applies only if MySQL was built using OpenSSL.

有关 sha256_password 和 caching_sha2_password 插件的信息，请参见 第 8.4.1.3 节，“SHA-256 可插拔认证” 和 第 8.4.1.2 节，“缓存 SHA-2 可插拔认证”。For information about the sha256_password and caching_sha2_password plugins, see Section 8.4.1.3, “SHA-256 Pluggable Authentication”, and Section 8.4.1.2, “Caching SHA-2 Pluggable Authentication”.

--socket=path，-S path --socket=path, -S path

用于连接localhost时，使用的 Unix 套接字文件，或者在 Windows 上使用的命名管道的名称。For connections to localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.

在 Windows 上，此选项仅在服务器启用支持命名管道连接的 named_pipe 系统变量启动时才适用。此外，进行连接的用户必须是由 named_pipe_full_access_group 系统变量指定的 Windows 组的成员。On Windows, this option applies only if the server was started with the named_pipe system variable enabled to support named-pipe connections. In addition, the user making the connection must be a member of the Windows group specified by the named_pipe_full_access_group system variable.

--ssl*

以--ssl开头的选项指定是否使用加密连接到服务器，并指示在哪里可以找到 SSL 密钥和证书。请参阅 加密连接的命令选项。Options that begin with --ssl specify whether to connect to the server using encryption and indicate where to find SSL keys and certificates. See Command Options for Encrypted Connections.

--ssl-fips-mode={OFF|ON|STRICT}

控制是否在客户端启用 FIPS 模式。 --ssl-fips-mode 选项与其他 --ssl-xxx 选项不同，因为它不用于建立加密连接，而是用于影响允许哪些加密操作。请参阅第 8.8 节“FIPS 支持”。Controls whether to enable FIPS mode on the client side. The --ssl-fips-mode option differs from other --ssl-xxx options in that it is not used to establish encrypted connections, but rather to affect which cryptographic operations to permit. See Section 8.8, “FIPS Support”.

这些 --ssl-fips-mode 值是允许的：These --ssl-fips-mode values are permitted:

此选项已弃用。预计将在未来的 MySQL 版本中移除。This option is deprecated. Expect it to be removed in a future version of MySQL.

--tls-ciphersuites=ciphersuite_list

用于 TLSv1.3 加密连接的允许密码套件。该值是一个或多个用冒号分隔的密码套件名称的列表。此选项可指定的密码套件取决于用于编译 MySQL 的 SSL 库。有关详细信息，请参见 第 8.3.2 节，“加密连接的 TLS 协议和密码”。The permissible ciphersuites for encrypted connections that use TLSv1.3. The value is a list of one or more colon-separated ciphersuite names. The ciphersuites that can be named for this option depend on the SSL library used to compile MySQL. For details, see Section 8.3.2, “Encrypted Connection TLS Protocols and Ciphers”.

--tls-sni-servername=server_name

如果指定了名称，该名称将通过 mysql_options() 的 MYSQL_OPT_TLS_SNI_SERVERNAME 选项传递给 libmysqlclient C API 库。服务器名称不区分大小写。要显示客户端为当前会话指定的服务器名称（如果有），请检查 Tls_sni_server_name 状态变量。When specified, the name is passed to the libmysqlclient C API library using the MYSQL_OPT_TLS_SNI_SERVERNAME option of mysql_options(). The server name is not case-sensitive. To show which server name the client specified for the current session, if any, check the Tls_sni_server_name status variable.

服务器名称指示（SNI）是 TLS 协议的一个扩展（必须使用支持 TLS 扩展的 OpenSSL 编译此选项才能生效）。MySQL 对 SNI 的实现仅代表客户端。Server Name Indication (SNI) is an extension to the TLS protocol (OpenSSL must be compiled using TLS extensions for this option to function). The MySQL implementation of SNI represents the client-side only.

--tls-version=protocol_list

用于加密连接的允许 TLS 协议。值是一个或多个以逗号分隔的协议名称列表。此选项可指定的协议取决于用于编译 MySQL 的 SSL 库。详情请参见 第 8.3.2 节，“加密连接 TLS 协议和密码”。The permissible TLS protocols for encrypted connections. The value is a list of one or more comma-separated protocol names. The protocols that can be named for this option depend on the SSL library used to compile MySQL. For details, see Section 8.3.2, “Encrypted Connection TLS Protocols and Ciphers”.

--user=user_name, -u user_name --user=user_name, -u user_name

用于连接服务器的 MySQL 帐户用户名。The user name of the MySQL account to use for connecting to the server.

如果您使用 Rewriter 插件，则应授予此用户 SKIP_QUERY_REWRITE 权限。If you are using the Rewriter plugin, you should grant this user the SKIP_QUERY_REWRITE privilege.

--zstd-compression-level=level --zstd-compression-level=level

用于与服务器连接时使用 zstd 压缩算法的压缩级别。允许的级别从 1 到 22，数值越大表示压缩级别越高。默认的 zstd 压缩级别为 3。对于不使用 zstd 压缩的连接，压缩级别设置没有效果。The compression level to use for connections to the server that use the zstd compression algorithm. The permitted levels are from 1 to 22, with larger values indicating increasing levels of compression. The default zstd compression level is 3. The compression level setting has no effect on connections that do not use zstd compression.

更多信息，请参阅 第 6.2.8 节，“连接压缩控制”。For more information, see Section 6.2.8, “Connection Compression Control”.

--defaults-extra-file=file_name --defaults-extra-file=file_name

在全局选项文件之后读取此选项文件，但（在 Unix 系统上）在用户选项文件之前。如果该文件不存在或无法访问，将发生错误。如果 file_name 不是绝对路径名，则相对于当前目录解释。Read this option file after the global option file but (on Unix) before the user option file. If the file does not exist or is otherwise inaccessible, an error occurs. If file_name is not an absolute path name, it is interpreted relative to the current directory.

有关此选项文件选项及其他选项文件选项的更多信息，请参见 第 6.2.2.3 节，“影响选项文件处理的命令行选项”。For additional information about this and other option-file options, see Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”.

--defaults-file=file_name --defaults-file=file_name

仅使用指定的选项文件。如果文件不存在或无法访问，将会发生错误。如果file_name不是绝对路径名，则将其相对于当前目录解释。Use only the given option file. If the file does not exist or is otherwise inaccessible, an error occurs. If file_name is not an absolute path name, it is interpreted relative to the current directory.

例外：即使使用--defaults-file，客户端程序仍会读取.mylogin.cnf。Exception: Even with --defaults-file, client programs read .mylogin.cnf.

有关此选项文件选项及其他选项文件选项的更多信息，请参见 第 6.2.2.3 节，“影响选项文件处理的命令行选项”。For additional information about this and other option-file options, see Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”.

--defaults-group-suffix=str --defaults-group-suffix=str

不仅读取常用选项组，还读取具有常用名称和后缀 str 的组。例如，mysqldump 通常读取 [client] 和 [mysqldump] 组。如果此选项指定为 --defaults-group-suffix=_other，则 mysqldump 也会读取 [client_other] 和 [mysqldump_other] 组。Read not only the usual option groups, but also groups with the usual names and a suffix of str. For example, mysqldump normally reads the [client] and [mysqldump] groups. If this option is given as --defaults-group-suffix=_other, mysqldump also reads the [client_other] and [mysqldump_other] groups.

有关此选项文件选项及其他选项文件选项的更多信息，请参见 第 6.2.2.3 节，“影响选项文件处理的命令行选项”。For additional information about this and other option-file options, see Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”.

--no-defaults

不读取任何选项文件。如果由于从选项文件中读取未知选项而导致程序启动失败，可以使用--no-defaults来阻止读取它们。Do not read any option files. If program startup fails due to reading unknown options from an option file, --no-defaults can be used to prevent them from being read.

例外是.mylogin.cnf文件（如果存在）在所有情况下都会被读取。即使使用 --no-defaults，这也允许以比命令行更安全的方式指定密码。要创建 .mylogin.cnf，请使用 mysql_config_editor 实用程序。请参阅第 6.6.7 节“mysql_config_editor — MySQL 配置实用程序”。The exception is that the .mylogin.cnf file is read in all cases, if it exists. This permits passwords to be specified in a safer way than on the command line even when --no-defaults is used. To create .mylogin.cnf, use the mysql_config_editor utility. See Section 6.6.7, “mysql_config_editor — MySQL Configuration Utility”.

有关此选项文件选项及其他选项文件选项的更多信息，请参见 第 6.2.2.3 节，“影响选项文件处理的命令行选项”。For additional information about this and other option-file options, see Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”.

--print-defaults

打印程序名称以及它从选项文件中获取的所有选项。Print the program name and all options that it gets from option files.

有关此选项文件选项及其他选项文件选项的更多信息，请参见 第 6.2.2.3 节，“影响选项文件处理的命令行选项”。For additional information about this and other option-file options, see Section 6.2.2.3, “Command-Line Options that Affect Option-File Handling”.

--add-drop-database

Write a DROP DATABASE statement before each CREATE DATABASE statement. This option is typically used in conjunction with the --all-databases或者--databases option because no CREATE DATABASE statements are written unless one of those options is specified.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

写一个DROP TABLE 语句位于每个 CREATE TABLE 语句之前。Write a DROP TABLE statement before each CREATE TABLE statement.

--add-drop-trigger

编写一个DROP TRIGGER 语句位于每个 CREATE TRIGGER 语句之前。Write a DROP TRIGGER statement before each CREATE TRIGGER statement.

--all-tablespaces, -Y

将创建所使用的任何表空间所需的所有 SQL 语句添加到表转储中通过 NDB 表。此信息不会以其他方式包含在 mysqldump 的输出中。此选项目前仅与 NDB Cluster 表相关。Adds to a table dump all SQL statements needed to create any tablespaces used by an NDB table. This information is not otherwise included in the output from mysqldump. This option is currently relevant only to NDB Cluster tables.

--no-create-db, -n

Suppress the CREATE DATABASE statements that are otherwise included in the output if the --databases或者--all-databases option is given.Suppress the CREATE DATABASE statements that are otherwise included in the output if the --databases or --all-databases option is given.

--no-create-info, -t

不要编写创建每个转储的 CREATE TABLE 语句Do not write CREATE TABLE statements that create each dumped table.

--no-tablespaces，-y --no-tablespaces, -y

此选项禁止所有 CREATE LOGFILE GROUP 和 CREATE TABLESPACE 语句。This option suppresses all CREATE LOGFILE GROUP and CREATE TABLESPACE statements in the output of mysqldump.

--replace

编写 REPLACE 语句而不是 INSERT 语句。Write REPLACE statements rather than INSERT statements.

--allow-keywords

允许创建作为关键字的列名称。这是通过在每个列名前加上表名来实现的。Permit creation of column names that are keywords. This works by prefixing each column name with the table name.

--comments, -i

在转储文件中写入附加信息，例如程序版本、服务器版本和主机。默认情况下启用此选项。要隐藏此附加信息，请使用 --skip-comments。Write additional information in the dump file such as program version, server version, and host. This option is enabled by default. To suppress this additional information, use --skip-comments.

--debug[=debug_options], -# [debug_options]

写入调试日志。典型的 debug_options 字符串是 d:t:o,file_name。默认值为 d:t:o,/tmp/mysqldump.trace。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.

此选项仅在 MySQL 使用 WITH_DEBUG 构建时可用。Oracle 提供的 MySQL 发行版二进制文件 未 使用此选项构建。This option is available only if MySQL was built using WITH_DEBUG. MySQL release binaries provided by Oracle are not built using this option.

--debug-check

程序退出时打印一些调试信息。Print some debugging information when the program exits.

此选项仅在 MySQL 使用 WITH_DEBUG 构建时可用。Oracle 提供的 MySQL 发行版二进制文件 未 使用此选项构建。This option is available only if MySQL was built using WITH_DEBUG. MySQL release binaries provided by Oracle are not built using this option.

--debug-info

在程序退出时打印调试信息以及内存和 CPU 使用情况统计。Print debugging information and memory and CPU usage statistics when the program exits.

此选项仅在 MySQL 使用 WITH_DEBUG 构建时可用。Oracle 提供的 MySQL 发行版二进制文件 未 使用此选项构建。This option is available only if MySQL was built using WITH_DEBUG. MySQL release binaries provided by Oracle are not built using this option.

--dump-date

如果给出 --comments 选项，mysqldump 在转储末尾生成以下形式的注释：If the --comments option is given, mysqldump produces a comment at the end of the dump of the following form:

-- Dump completed on DATE

但是，日期会导致不同时间获取的转储文件看起来不同，即使数据在其他方面相同。 --dump-date 和 --skip-dump-date 控制是否将日期添加到注释中。默认值为 --dump-date （在注释中包含日期）。 --skip-dump-date 禁止打印日期。However, the date causes dump files taken at different times to appear to be different, even if the data are otherwise identical. --dump-date and --skip-dump-date control whether the date is added to the comment. The default is --dump-date (include the date in the comment). --skip-dump-date suppresses date printing.

--force, -f

忽略所有错误；即使在表转储期间发生 SQL 错误，也可以继续。Ignore all errors; continue even if an SQL error occurs during a table dump.

此选项的一个用途是使 mysqldump 继续执行，即使它遇到因定义引用已删除的表而变得无效的视图。如果没有 --force，mysqldump 将退出并显示错误消息。使用 --force，mysqldump 打印错误消息，但它还会将包含视图定义的 SQL 注释写入转储输出并继续执行。One use for this option is to cause mysqldump to continue executing even when it encounters a view that has become invalid because the definition refers to a table that has been dropped. Without --force, mysqldump exits with an error message. With --force, mysqldump prints the error message, but it also writes an SQL comment containing the view definition to the dump output and continues executing.

如果 --ignore-error 选项还可以忽略特定错误，--force 优先。If the --ignore-error option is also given to ignore specific errors, --force takes precedence.

--log-error=file_name --log-error=file_name

通过将警告和错误附加到指定文件来记录它们。默认情况下不进行日志记录。Log warnings and errors by appending them to the named file. The default is to do no logging.

--skip-comments

请参阅 --comments 选项。See the description for the --comments option.

--verbose, -v

详细模式。打印有关程序执行内容的更多信息。Verbose mode. Print more information about what the program does.

--help, -?

显示帮助信息并退出。Display a help message and exit.

--version, -V

显示版本信息并退出。Display version information and exit.

--character-sets-dir=dir_name --character-sets-dir=dir_name

安装字符集的目录。请参见第 12.15 节，“字符集配置”。The directory where character sets are installed. See Section 12.15, “Character Set Configuration”.

--default-character-set=charset_name --default-character-set=charset_name

使用charset_name作为默认字符集。请参见第 12.15 节“字符集配置”。如果未指定字符集，mysqldump 使用 utf8mb4。Use charset_name as the default character set. See Section 12.15, “Character Set Configuration”. If no character set is specified, mysqldump uses utf8mb4.

--no-set-names, -N

关闭--set-charset 设置，与指定 --skip-set-charset 相同。Turns off the --set-charset setting, the same as specifying --skip-set-charset.

--set-charset

将 SET NAMES default_character_set 写入输出。默认情况下启用此选项。要禁止使用 SET NAMES 语句，请使用 --skip-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.

--apply-replica-statements

对于使用 --dump-replica 选项生成的副本转储，此选项添加 STOP REPLICA 语句位于带有二进制日志坐标的语句之前，START REPLICA 语句位于输出末尾。For a replica dump produced with the --dump-replica option, this option adds a STOP REPLICA statement before the statement with the binary log coordinates, and a START REPLICA statement at the end of the output.

--apply-slave-statements

这是 --apply-replica-statements。This is a deprecated alias for --apply-replica-statements.

--delete-source-logs

在复制源服务器上，通过发送 PURGE BINARY LOGS语句。这些选项需要 RELOAD 权限以及足以执行该语句的权限。此选项自动启用 --source-data。On a replication source server, delete the binary logs by sending a PURGE BINARY LOGS statement to the server after performing the dump operation. The options require the RELOAD privilege as well as privileges sufficient to execute that statement. This option automatically enables --source-data.

--delete-master-logs

这是 --delete-source-logs。This is a deprecated alias for --delete-source-logs.

--dump-replica[=value] --dump-replica[=value]

This option is similar to --source-data, except that it is used to dump a replica server to produce a dump file that can be used to set up another server as a replica that has the same source as the dumped server. The option causes the dump output to include a CHANGE REPLICATION SOURCE TO statement that indicates the binary log coordinates (file name and position) of the dumped replica's source. The CHANGE REPLICATION SOURCE TO statement reads the values of Relay_Master_Log_File以及Exec_Master_Log_Pos from the SHOW REPLICA STATUS output and uses them for SOURCE_LOG_FILE以及SOURCE_LOG_POS respectively. These are the replication source server coordinates from which the replica starts replicating.This option is similar to --source-data, except that it is used to dump a replica server to produce a dump file that can be used to set up another server as a replica that has the same source as the dumped server. The option causes the dump output to include a CHANGE REPLICATION SOURCE TO statement that indicates the binary log coordinates (file name and position) of the dumped replica's source. The CHANGE REPLICATION SOURCE TO statement reads the values of Relay_Master_Log_File and Exec_Master_Log_Pos from the SHOW REPLICA STATUS output and uses them for SOURCE_LOG_FILE and SOURCE_LOG_POS respectively. These are the replication source server coordinates from which the replica starts replicating.

--dump-replica 会导致使用源坐标而不是转储服务器的坐标，如下所示由 --source-data 选项完成。此外，指定此选项会覆盖--source-data选项。--dump-replica causes the coordinates from the source to be used rather than those of the dumped server, as is done by the --source-data option. In addition, specifying this option overrides the --source-data option.

选项值的处理方式与--source-data相同。设置不值或设置 1 会导致 CHANGE REPLICATION SOURCE TO 语句写入转储。设置 2 会导致语句被写入但包含在 SQL 注释中。在启用或禁用其他选项以及如何处理锁定方面，它与 --source-data 具有相同的效果。The option value is handled the same way as for --source-data. Setting no value or 1 causes a CHANGE REPLICATION SOURCE TO statement to be written to the dump. Setting 2 causes the statement to be written but encased in SQL comments. It has the same effect as --source-data in terms of enabling or disabling other options and in how locking is handled.

--dump-replica 导致 mysqldump 停止复制转储之前的 SQL 线程，然后重新启动它。--dump-replica causes mysqldump to stop the replication SQL thread before the dump and restart it again after.

--dump-replica 向服务器发送一个 SHOW REPLICA STATUS 语句来获取信息，因此它们需要足够的权限来执行该语句--dump-replica sends a SHOW REPLICA STATUS statement to the server to obtain information, so they require privileges sufficient to execute that statement.

--apply-replica-statements 和 --include-source-host-port 选项可以与 --dump-replica.--apply-replica-statements and --include-source-host-port options can be used in conjunction with --dump-replica.

--dump-slave[=value] --dump-slave[=value]

这是 --dump-replica 的已弃用别名。This is a deprecated alias for --dump-replica.

--include-source-host-port

添加主机名和 TCP/IP 端口号的 SOURCE_HOST 和 SOURCE_PORT 选项副本源的 CHANGE REPLICATION SOURCE TO 语句位于使用 --dump-replica 选项。Adds the SOURCE_HOST and SOURCE_PORT options for the host name and TCP/IP port number of the replica's source, to the CHANGE REPLICATION SOURCE TO statement in a replica dump produced with the --dump-replica option.

--include-master-host-port

这是 --include-source-host-port 的已弃用别名。This is a deprecated alias for --include-source-host-port.

--master-data[=value] --master-data[=value]

这是 --source-data.This is a deprecated alias for --source-data.

--output-as-version=value --output-as-version=value

确定与副本和事件相关的语句所使用的术语级别，从而可以创建与不接受新术语的旧版本 MySQL 兼容的转储。此选项可以采用以下任一值，其效果如下所列：Determines the level of terminology used for statements relating to replicas and events, making it possible to create dumps compatible with older versions of MySQL that do not accept the newer terminology. This option can take any one of the following values, with effects described as listed here:

此选项影响 --events，--dump-replica，--source-data，--apply-replica-statements 和 --include-source-host-port。This option affects the output from --events, --dump-replica, --source-data, --apply-replica-statements, and --include-source-host-port.

--source-data[=value] --source-data[=value]

用于转储复制源服务器以生成转储文件，该文件可用于将另一台服务器设置为复制源服务器的副本来源。这些选项导致转储输出包含 CHANGE REPLICATION SOURCE TO 语句，该语句指示转储服务器的二进制日志坐标（文件名和位置）。这些是复制源服务器坐标，在将转储文件加载到副本中后，副本应从该坐标开始复制。Used to dump a replication source server to produce a dump file that can be used to set up another server as a replica of the source. The options cause the dump output to include a CHANGE REPLICATION SOURCE TO statement that indicates the binary log coordinates (file name and position) of the dumped server. These are the replication source server coordinates from which the replica should start replicating after you load the dump file into the replica.

如果选项值为 2，则 CHANGE REPLICATION SOURCE TO 语句将被写入 SQL 注释，因此仅供参考；重新加载转储文件时它不起作用。如果该选项值为 1，则该语句不会作为注释写入，并在重新加载转储文件时生效。如果未指定选项值，则默认值为 1。If the option value is 2, the CHANGE REPLICATION SOURCE TO statement is written as an SQL comment, and thus is informative only; it has no effect when the dump file is reloaded. If the option value is 1, the statement is not written as a comment and takes effect when the dump file is reloaded. If no option value is specified, the default value is 1.

--source-data 向服务器发送 SHOW BINARY LOG STATUS 语句来获取信息，因此它们需要足够的权限才能执行那个声明。此选项还需要 RELOAD 权限，并且必须启用二进制日志。--source-data sends a SHOW BINARY LOG STATUS statement to the server to obtain information, so they require privileges sufficient to execute that statement. This option also requires the RELOAD privilege and the binary log must be enabled.

--source-data 自动关闭 --lock-tables。它们还会打开--lock-all-tables，除非还指定了--single-transaction，在这种情况下，仅在短时间内获取全局读锁转储的开始（请参阅 --single-transaction 的说明）。在所有情况下，对日志的任何操作都会在转储的确切时刻发生。--source-data automatically turns off --lock-tables. They also turn on --lock-all-tables, unless --single-transaction also is specified, in which case, a global read lock is acquired only for a short time at the beginning of the dump (see the description for --single-transaction). In all cases, any action on logs happens at the exact moment of the dump.

还可以通过使用 --dump-replica 选项转储源的现有副本来设置副本，该选项会覆盖 --source-data 使其成为忽略。It is also possible to set up a replica by dumping an existing replica of the source, using the --dump-replica option, which overrides --source-data causing it to be ignored.

--set-gtid-purged=value --set-gtid-purged=value

此选项适用于使用基于 GTID 的复制 (gtid_mode=ON) 的服务器。它控制在转储输出中包含 SET @@GLOBAL.gtid_purged 语句，该语句更新重新加载转储文件的服务器上 gtid_purged 的值，以添加从源服务器的 gtid_executed 系统变量。 gtid_purged 保存已在服务器上应用的所有事务的 GTID，但不存在于服务器上的任何二进制日志文件中。 mysqldump 因此会添加在源服务器上执行的事务的 GTID，以便目标服务器按应用记录这些事务，尽管目标服务器的二进制日志中没有这些事务。 --set-gtid-purged 还控制包含 SET @@SESSION.sql_log_bin=0 语句，该语句在重新加载转储文件时禁用二进制日志记录。此语句可防止在转储文件执行时生成新的 GTID 并将其分配给转储文件中的事务，以便使用事务的原始 GTID。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 is reloaded, to add the GTID set from the source server's gtid_executed system variable. gtid_purged holds the GTIDs of all transactions that have been applied on the server, but do not exist on any binary log file on the server. mysqldump therefore adds the GTIDs for the transactions that were executed on the source server, so that the target server records these transactions as 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 prevents new GTIDs from being generated and assigned to the transactions in the dump file as they are executed, so that the original GTIDs for the transactions are used.

如果您未设置 --set-gtid-purged 选项，则默认情况下，如果您支持的服务器上启用了 GTID，转储输出中将包含 SET @@GLOBAL.gtid_purged 语句并且 gtid_executed 系统变量的全局值中的 GTID 集不为空。如果服务器上启用了 GTID，则还包含 SET @@SESSION.sql_log_bin=0 语句。If you do not set the --set-gtid-purged option, the default is that a SET @@GLOBAL.gtid_purged statement is included in the dump output if GTIDs are enabled on the server you are backing up, and the set of GTIDs in the global value of the gtid_executed system variable is not empty. A SET @@SESSION.sql_log_bin=0 statement is also included if GTIDs are enabled on the server.

您可以将 gtid_purged 的值替换为指定的 GTID 集，或者在语句中添加加号 (+) 以将指定的 GTID 集附加到 gtid_purged 已持有的 GTID 集。 mysqldump 记录的 SET @@GLOBAL.gtid_purged 语句在特定于版本的注释中包含一个加号 (+)，这样 MySQL 将转储文件中设置的 GTID 添加到现有的 gtid_purged 值。You can either replace the value of gtid_purged with a specified GTID set, or add a plus sign (+) to the statement to append a specified GTID set to the GTID set that is already held by gtid_purged. The SET @@GLOBAL.gtid_purged statement recorded by mysqldump includes a plus sign (+) in a version-specific comment, such that MySQL adds the GTID set from the dump file to the existing gtid_purged value.

需要注意的是， SET @@GLOBAL.gtid_purged 语句的 mysqldump 包含的值包括 gtid_executed 在服务器上设置，甚至更改了数据库的受抑制部分或服务器上未包含在部分转储中的其他数据库。这可能意味着在重播转储文件的服务器上更新 gtid_purged 值后，存在与目标服务器上任何数据不相关的 GTID。如果不在目标服务器上重播任何进一步的转储文件，无关的 GTID 不会对服务器的未来操作造成任何问题，但它们会使复制拓扑中不同服务器上的 GTID 集进行比较或协调变得更加困难。如果您确实在目标服务器上重播包含相同 GTID 的进一步转储文件（例如，来自同一源服务器的另一个部分转储），则第二个转储文件中的任何 SET @@GLOBAL.gtid_purged 语句都会失败。在这种情况下，请在重播转储文件之前手动删除该语句，或者输出不包含该语句的转储文件。It is important to note that the value that is included by mysqldump for the SET @@GLOBAL.gtid_purged statement includes the GTIDs of all transactions in the gtid_executed set on the server, even those that changed suppressed parts of the database, or other databases on the server that were not included in a partial dump. This can mean that after the gtid_purged value has been updated on the server where the dump file is replayed, GTIDs are present that do not relate to any data on the target server. If you do not replay any further dump files on the target server, the extraneous GTIDs do not cause any problems with the future operation of the server, but they make it harder to compare or reconcile GTID sets on different servers in the replication topology. If you do replay a further dump file on the target server that contains the same GTIDs (for example, another partial dump from the same origin server), any SET @@GLOBAL.gtid_purged statement in the second dump file fails. In this case, either remove the statement manually before replaying the dump file, or output the dump file without the statement.

如果 SET @@GLOBAL.gtid_purged 语句在目标服务器上没有所需的结果，您可以从输出中排除该语句，或者包含该语句但将其注释掉，以便它不会自动执行。您还可以包含该语句，但在转储文件中手动编辑它以获得所需的结果。If the SET @@GLOBAL.gtid_purged statement would not have the desired result on your target server, you can exclude the statement from the output, or include it but comment it out so that it is not actioned automatically. You can also include the statement but manually edit it in the dump file to achieve the desired result.

--set-gtid-purged 选项的可能值如下：The possible values for the --set-gtid-purged option are as follows:

--compact

产生更紧凑的输出。此选项启用 --skip-add-drop-table、--skip-add-locks、--skip-comments、--skip-disable-keys 和 --skip-set-charset 选项。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=name --compatible=name

生成与其他数据库系统或较旧的 MySQL 服务器更兼容的输出。该选项唯一允许的值为 ansi，它与设置服务器 SQL 模式的相应选项具有相同的含义。请参阅第 7.1.11 节“服务器 SQL 模式”。Produce output that is more compatible with other database systems or with older MySQL servers. The only permitted value for this option is ansi, which has the same meaning as the corresponding option for setting the server SQL mode. See Section 7.1.11, “Server SQL Modes”.

--complete-insert, -c

使用包含列名称的完整 INSERT 语句。Use complete INSERT statements that include column names.

--create-options

在 CREATE TABLE 语句。Include all MySQL-specific table options in the CREATE TABLE statements.

--fields-terminated-by=..., --fields-enclosed-by=..., --fields-optionally-enclosed-by=..., --fields-escaped-by=...

这些选项与--tab选项一起使用，含义与相应的FIELDS条款用于LOAD DATA。参见第 15.2.9 节，“LOAD DATA 语句”.These options are used with the --tab option and have the same meaning as the corresponding FIELDS clauses for LOAD DATA. See Section 15.2.9, “LOAD DATA Statement”.

--hex-blob

使用十六进制表示法转储二进制列（例如，'abc' 变为 0x616263）。受影响的数据类型为 BINARY、VARBINARY、 BLOB 类型、BIT、所有空间数据类型以及与 binary字符集。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.

该--hex-blob当使用时，选项会被忽略--tab使用。The --hex-blob option is ignored when the --tab is used.

--lines-terminated-by=...

此选项与--tab选项一起使用，其含义与相应的LINES条款用于LOAD DATA。参见第 15.2.9 节，“LOAD DATA 语句”.This option is used with the --tab option and has the same meaning as the corresponding LINES clause for LOAD DATA. See Section 15.2.9, “LOAD DATA Statement”.

--quote-names, -Q

在 ` 字符内引用标识符（例如数据库、表和列名称）。如果启用 ANSI_QUOTES SQL 模式，标识符会在 " 字符内加引号。此选项默认启用。可以使用 --skip-quote-names 禁用它，但应在任何选项（例如 --compatible，可能会启用--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, but this option should be given after any option such as --compatible that may enable --quote-names.

--result-file=file_name, -r file_name --result-file=file_name, -r file_name

直接输出到指定文件。即使在生成转储时发生错误，也会创建结果文件并覆盖其先前的内容。Direct output to the named file. The result file is created and its previous contents overwritten, even if an error occurs while generating the dump.

应在 Windows 上使用此选项，以防止换行 \n 字符转换为 \r\n 回车/换行序列。This option should be used on Windows to prevent newline \n characters from being converted to \r\n carriage return/newline sequences.

--show-create-skip-secondary-engine=value --show-create-skip-secondary-engine=value

从SECONDARY ENGINE语句中排除CREATE TABLE条款。它通过在转储操作期间启用show_create_table_skip_secondary_engine系统变量来实现。此外，您可以在使用之前启用show_create_table_skip_secondary_engine系统变量mysqldump.Excludes the SECONDARY ENGINE clause from CREATE TABLE statements. It does so by enabling the show_create_table_skip_secondary_engine system variable for the duration of the dump operation. Alternatively, you can enable the show_create_table_skip_secondary_engine system variable prior to using mysqldump.

--tab=dir_name, -T dir_name --tab=dir_name, -T dir_name

生成制表符分隔的文本格式数据文件。对于每个转储的表，mysqldump 创建一个 tbl_name.sql 文件，其中包含 CREATE TABLE 语句用于创建表，服务器写入包含其数据的 tbl_name.txt 文件。选项值是写入文件的目录。Produce tab-separated text-format data files. For each dumped table, mysqldump creates a tbl_name.sql file that contains the CREATE TABLE statement that creates the table, and the server writes a tbl_name.txt file that contains its data. The option value is the directory in which to write the files.

默认情况下，.txt 数据文件的格式在列之间使用制表符值和每行末尾的换行符。可以使用 --fields-xxx 和 --lines-terminated-by 选项显式指定格式。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.

列值将转换为 --default-character-set 选项。Column values are converted to the character set specified by the --default-character-set option.

--tz-utc

此选项允许在不同时区的服务器之间转储和重新加载TIMESTAMP 列。 mysqldump 将其连接时区设置为 UTC 并将 SET TIME_ZONE='+00:00' 添加到转储文件中。如果没有此选项，TIMESTAMP 列将在源服务器和目标服务器本地的时区中转储和重新加载，如果服务器位于不同的时区，这可能会导致值发生更改。 --tz-utc 还可以防止夏令时导致的更改。默认情况下启用 --tz-utc。要禁用它，请使用 --skip-tz-utc。This option enables TIMESTAMP columns to be dumped and reloaded between servers in different time zones. mysqldump sets its connection time zone to UTC and adds SET TIME_ZONE='+00:00' to the dump file. Without this option, TIMESTAMP columns are dumped and reloaded in the time zones local to the source and destination servers, which can cause the values to change if the servers are in different time zones. --tz-utc also protects against changes due to daylight saving time. --tz-utc is enabled by default. To disable it, use --skip-tz-utc.

--xml, -X

将转储输出写入格式正确的 XML。Write dump output as well-formed XML.

NULL、'NULL' 和空值：对于名为 column_name 的列，NULL 值、空字符串和字符串值 'NULL' 为在此选项生成的输出中相互区分如下。NULL, 'NULL', and Empty Values: For a column named column_name, the NULL value, an empty string, and the string value 'NULL' are distinguished from one another in the output generated by this option as follows.

从mysql客户端运行时的输出--xml选项也遵循前述规则。（见第 6.5.1.1 节，“mysql 客户端选项”.)The output from the mysql client when run using the --xml option also follows the preceding rules. (See Section 6.5.1.1, “mysql Client Options”.)

mysqldump 包括 XML 命名空间，如下所示：XML output from mysqldump includes the XML namespace, as shown here:

$> 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>

--all-databases, -A

转储所有表中的所有表数据库。这与使用 --databases 选项并在命令行上命名所有数据库相同。Dump all tables in all databases. This is the same as using the --databases option and naming all the databases on the command line.

Prior to MySQL 8.4, the --routines以及--events选项进行更改。mysqldump were not required to include stored routines and events when using the --all-databases option: The dump included the mysql system database, and therefore also the mysql.proc以及mysql.event tables containing stored routine and event definitions. As of MySQL 8.4, the mysql.event以及mysql.proc tables are not used. Definitions for the corresponding objects are stored in data dictionary tables, but those tables are not dumped. To include stored routines and events in a dump made using --all-databases, use the --routines以及--events options explicitly.Prior to MySQL 8.4, the --routines and --events options for mysqldump were not required to include stored routines and events when using the --all-databases option: The dump included the mysql system database, and therefore also the mysql.proc and mysql.event tables containing stored routine and event definitions. As of MySQL 8.4, the mysql.event and mysql.proc tables are not used. Definitions for the corresponding objects are stored in data dictionary tables, but those tables are not dumped. To include stored routines and events in a dump made using --all-databases, use the --routines and --events options explicitly.

--databases, -B

转储多个数据库。通常，mysqldump 将命令行上的第一个名称参数视为数据库名称，将后面的名称视为表名称。使用此选项，它将所有名称参数视为数据库名称。 CREATE DATABASE 和 USE 语句包含在每个新数据库之前的输出中。Dump several databases. Normally, mysqldump treats the first name argument on the command line as a database name and following names as table names. With this option, it treats all name arguments as database names. CREATE DATABASE and USE statements are included in the output before each new database.

此选项可用于转储 performance_schema 数据库，即使使用 --all-databases 选项，通常也不会转储该数据库。 （还可以使用 --skip-lock-tables 选项。）This option may be used to dump the performance_schema database, which normally is not dumped even with the --all-databases option. (Also use the --skip-lock-tables option.)

--events, -E

在输出中包含转储数据库的事件计划程序事件。此选项需要这些数据库的 EVENT 权限。Include Event Scheduler events for the dumped databases in the output. This option requires the EVENT privileges for those databases.

使用 --events 生成的输出包含 CREATE EVENT 语句来创建事件。The output generated by using --events contains CREATE EVENT statements to create the events.

--ignore-error=error[,error]... --ignore-error=error[,error]...

忽略指定的错误。该选项值是逗号分隔的错误号列表，指定在 mysqldump 执行期间要忽略的错误。如果还指定了 --force 选项来忽略所有错误，则 --force 优先。Ignore the specified errors. The option value is a list of comma-separated error numbers specifying the errors to ignore during mysqldump execution. If the --force option is also given to ignore all errors, --force takes precedence.

--ignore-table=db_name.tbl_name --ignore-table=db_name.tbl_name

不要转储给定的表，该表必须使用数据库名称和表名称指定。要忽略多个表，请多次使用此选项。此选项还可用于忽略视图。Do not dump the given table, which must be specified using both the database and table names. To ignore multiple tables, use this option multiple times. This option also can be used to ignore views.

--ignore-views=boolean --ignore-views=boolean

跳过转储文件中的表视图。Skips table views in the dump file.

--init-command=str

连接到 MySQL 服务器后执行的单个 SQL 语句。该定义会重置由它或 init-command-add 定义的现有语句。Single SQL statement to execute after connecting to the MySQL server. The definition resets existing statements defined by it or init-command-add.

--init-command-add=str

添加一条额外的 SQL 语句，以便在连接或重新连接到 MySQL 服务器后执行。它可以在没有 --init-command 的情况下使用，但如果在它之前使用则无效，因为 init-command 会重置要调用的命令列表。Add an additional SQL statement to execute after connecting or reconnecting to the MySQL server. It's usable without --init-command but has no effect if used before it because init-command resets the list of commands to call.

--no-data, -d

不写入任何表行信息（即不转储表内容）。如果您只想转储表的 CREATE TABLE 语句（例如，通过加载转储文件创建表的空副本），这非常有用。Do not write any table row information (that is, do not dump table contents). This is useful if you want to dump only the CREATE TABLE statement for the table (for example, to create an empty copy of the table by loading the dump file).

--routines, -R

在输出中包含转储数据库的存储例程（过程和函数）。此选项需要全局 SELECT 权限。Include stored routines (procedures and functions) for the dumped databases in the output. This option requires the global SELECT privilege.

使用 --routines 生成的输出包含 CREATE PROCEDURE 和 CREATE FUNCTION 语句来创建例程。The output generated by using --routines contains CREATE PROCEDURE and CREATE FUNCTION statements to create the routines.

--skip-generated-invisible-primary-key

此选项会导致生成的不可见主键从输出中排除。有关详细信息，请参阅第 15.1.20.11 节“生成的不可见主键”。This option causes generated invisible primary keys to be excluded from the output. For more information, see Section 15.1.20.11, “Generated Invisible Primary Keys”.

--tables

覆盖 --databases 或 -B 选项。 mysqldump 将选项后面的所有名称参数视为表名称。Override the --databases or -B option. mysqldump regards all name arguments following the option as table names.

--triggers

在输出中包含每个转储表的触发器。该选项默认启用；使用 --skip-triggers 禁用它。Include triggers for each dumped table in the output. This option is enabled by default; disable it with --skip-triggers.

要能够转储表的触发器，您必须拥有该表的 TRIGGER 权限。To be able to dump a table's triggers, you must have the TRIGGER privilege for the table.

允许使用多个触发器。 mysqldump 按激活顺序转储触发器，以便在重新加载转储文件时，按相同的激活顺序创建触发器。但是，如果 mysqldump 转储文件包含具有相同触发事件和操作时间的表的多个触发器，则尝试将转储文件加载到不支持多个触发器的旧服务器时会发生错误。 （有关解决方法，请参阅降级说明；您可以转换触发器以与旧服务器兼容。）Multiple triggers are permitted. mysqldump dumps triggers in activation order so that when the dump file is reloaded, triggers are created in the same activation order. However, if a mysqldump dump file contains multiple triggers for a table that have the same trigger event and action time, an error occurs for attempts to load the dump file into an older server that does not support multiple triggers. (For a workaround, see Downgrade Notes; you can convert triggers to be compatible with older servers.)

--where='where_condition', -w 'where_condition'

仅转储由给定 WHERE 条件选择的行。如果条件包含空格或命令解释器特有的其他字符，则必须在条件周围加引号。Dump only rows selected by the given WHERE condition. Quotes around the condition are mandatory if it contains spaces or other characters that are special to your command interpreter.

示例：Examples:

--where="user='jimf'"
-w"userid>1"
-w"userid<1"

--column-statistics

将 ANALYZE TABLE 语句添加到输出中，以便在重新加载转储文件时生成转储表的直方图统计信息。默认情况下禁用此选项，因为大型表的直方图生成可能需要很长时间。Add ANALYZE TABLE statements to the output to generate histogram statistics for dumped tables when the dump file is reloaded. This option is disabled by default because histogram generation for large tables can take a long time.

--disable-keys, -K

对于每个表，将 INSERT 语句用 /*!40000 ALTER TABLE tbl_name DISABLE KEYS */; 和 /*!40000 ALTER TABLE tbl_name ENABLE KEYS */; 语句。这使得加载转储文件更快，因为索引是在插入所有行之后创建的。此选项仅对 MyISAM 表的非唯一索引有效。For each table, surround the INSERT statements with /*!40000 ALTER TABLE tbl_name DISABLE KEYS */; and /*!40000 ALTER TABLE tbl_name ENABLE KEYS */; statements. This makes loading the dump file faster because the indexes are created after all rows are inserted. This option is effective only for nonunique indexes of MyISAM tables.

--extended-insert, -e

使用包含多个 VALUES 列表的多行语法编写 INSERT 语句。这会导致转储文件更小，并加快文件重新加载时的插入速度。Write INSERT statements using multiple-row syntax that includes several VALUES lists. This results in a smaller dump file and speeds up inserts when the file is reloaded.

--insert-ignore

编写 INSERT IGNORE 语句，而不是 INSERT 语句。Write INSERT IGNORE statements rather than INSERT statements.

--max-allowed-packet=value --max-allowed-packet=value

客户端/服务器通信缓冲区的最大大小。默认为 24MB，最大为 1GB。The maximum size of the buffer for client/server communication. The default is 24MB, the maximum is 1GB.

--mysqld-long-query-time=value --mysqld-long-query-time=value

设置long_query_time 系统变量。如果您想增加 mysqldump 查询在记录到慢速查询日志文件之前所允许的时间，请使用此选项。 mysqldump 执行全表扫描，这意味着其查询通常会超出有用的全局 long_query_time 设置用于常规查询。默认全局设置为 10 秒。Set the session value of the long_query_time system variable. Use this option if you want to increase the time allowed for queries from mysqldump before they are logged to the slow query log file. mysqldump performs a full table scan, which means its queries can often exceed a global long_query_time setting that is useful for regular queries. The default global setting is 10 seconds.

您可以使用 --mysqld-long-query-time 指定从 0 开始的会话值（这意味着来自 mysqldump 记录到慢查询日志）为 31536000，即 365 天（以秒为单位）。对于 mysqldump 的选项，您只能指定整秒。如果不指定此选项，服务器的全局设置将应用于mysqldump 的查询。You can use --mysqld-long-query-time to specify a session value from 0 (meaning that every query from mysqldump is logged to the slow query log) to 31536000, which is 365 days in seconds. For mysqldump’s option, you can only specify whole seconds. When you do not specify this option, the server’s global setting applies to mysqldump’s queries.

--net-buffer-length=value --net-buffer-length=value

客户端/服务器通信缓冲区的初始大小。创建多行 INSERT 语句时（与 --extended-insert 或 --opt 选项），mysqldump 创建最多 --net-buffer-length 字节长。如果增加此变量，请确保 MySQL 服务器 net_buffer_length 系统变量的值至少有这么大。The initial size of the buffer for client/server communication. When creating multiple-row INSERT statements (as with the --extended-insert or --opt option), mysqldump creates rows up to --net-buffer-length bytes long. If you increase this variable, ensure that the MySQL server net_buffer_length system variable has a value at least this large.

--network-timeout, -M

通过设置 --max-allowed-packet 为其最大值，网络读写超时为较大值。默认情况下启用此选项。要禁用它，请使用 --skip-network-timeout。Enable large tables to be dumped by setting --max-allowed-packet to its maximum value and network read and write timeouts to a large value. This option is enabled by default. To disable it, use --skip-network-timeout.

--opt

此选项默认启用，是 --add-drop-table --add-locks --create-options --disable-keys --extended-insert --lock-tables --quick --set-charset。它提供快速转储操作并生成可以快速重新加载到 MySQL 服务器的转储文件。This option, enabled by default, is shorthand for the combination of --add-drop-table --add-locks --create-options --disable-keys --extended-insert --lock-tables --quick --set-charset. It gives a fast dump operation and produces a dump file that can be reloaded into a MySQL server quickly.

由于 --opt 选项默认启用，因此您只需指定其相反的 --skip-opt 即可关闭多个默认设置。有关选择性启用或禁用受 --opt 影响的选项子集的信息，请参阅 mysqldump 选项组 的讨论。Because the --opt option is enabled by default, you only specify its converse, the --skip-opt to turn off several default settings. See the discussion of mysqldump option groups for information about selectively enabling or disabling a subset of the options affected by --opt.

--quick, -q

此选项对于转储大型表很有用。它强制 mysqldump 从服务器一次一行检索表中的行，而不是检索整个行集并在将其写出之前将其缓冲在内存中。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.

--skip-opt

请参阅 --opt 选项的说明。See the description for the --opt option.

--add-locks

用 LOCK TABLES 和 UNLOCK TABLES 语句。这会导致重新加载转储文件时插入速度更快。请参阅第 10.2.5.1 节“优化 INSERT 语句”。Surround each table dump with LOCK TABLES and UNLOCK TABLES statements. This results in faster inserts when the dump file is reloaded. See Section 10.2.5.1, “Optimizing INSERT Statements”.

--flush-logs, -F

在开始转储之前刷新 MySQL 服务器日志文件。此选项需要 RELOAD 权限。如果将此选项与 --all-databases 选项结合使用，则对于每个转储的数据库都会刷新日志。例外情况是使用 --lock-all-tables、--source-data 或 --single-transaction。在这些情况下，日志仅刷新一次，对应于所有表被 FLUSH TABLES WITH READ LOCK 锁定的时刻。如果您希望转储和日志刷新在完全相同的时刻发生，则应将 --flush-logs 与 --lock-all-tables、--source-data，或--single-transaction。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, --source-data, or --single-transaction. In these cases, 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, --source-data, or --single-transaction.

--flush-privileges

转储 mysql 数据库后，将 FLUSH PRIVILEGES 语句添加到转储输出中。每当转储包含 mysql 数据库以及依赖于 mysql 数据库中的数据才能正确恢复的任何其他数据库时，都应使用此选项。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.

由于转储文件包含 FLUSH PRIVILEGES 语句，因此重新加载文件需要足够的权限执行该语句。Because the dump file contains a FLUSH PRIVILEGES statement, reloading the file requires privileges sufficient to execute that statement.

--lock-all-tables, -x

锁定所有数据库中的所有表。这是通过在整个转储期间获取全局读锁来实现的。此选项会自动关闭 --single-transaction 和 --lock-tables。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.

--lock-tables, -l

对于每个转储的数据库，在转储之前锁定所有要转储的表。这些表使用READ LOCAL 锁定，以允许在MyISAM 表的情况下进行并发插入。对于诸如 InnoDB 之类的事务表，--single-transaction 是比 --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-tables 分别锁定每个数据库的表，此选项不保证转储文件中的表在数据库之间逻辑一致。不同数据库中的表可能会以完全不同的状态转储。Because --lock-tables locks tables for each database separately, this option does not guarantee that the tables in the dump file are logically consistent between databases. Tables in different databases may be dumped in completely different states.

某些选项，例如--opt，会自动启用--lock-tables。如果要覆盖此设置，请在选项列表末尾使用 --skip-lock-tables。Some options, such as --opt, automatically enable --lock-tables. If you want to override this, use --skip-lock-tables at the end of the option list.

--no-autocommit

将每个转储表的 INSERT 语句括在 SET autocommit = 0 和 COMMIT 语句。Enclose the INSERT statements for each dumped table within SET autocommit = 0 and COMMIT statements.

--order-by-primary

每张表的行按其主键排序，或者如果存在，则按其第一个唯一索引排序。将表MyISAM导出以便加载到InnoDB表时，这非常有用，但会显著增加导出操作所需时间。Dump each table's rows sorted by its primary key, or by its first unique index, if such an index exists. This is useful when dumping a MyISAM table to be loaded into an InnoDB table, but makes the dump operation take considerably longer.

--shared-memory-base-name=name --shared-memory-base-name=name

在 Windows 上，通过共享内存连接到本地服务器时使用的共享内存名称。默认值是 MYSQL。共享内存名称区分大小写。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.

此选项仅在服务器启用了 shared_memory 系统变量以支持共享内存连接时适用。This option applies only if the server was started with the shared_memory system variable enabled to support shared-memory connections.

--single-transaction

此选项将事务隔离模式设置为 REPEATABLE READ 并发送 START TRANSACTION 在转储数据之前向服务器发送 SQL 语句。它仅对诸如 InnoDB 之类的事务表有用，因为这样它会在发出 START 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.

RELOAD 或 FLUSH_TABLES 权限需要 --single-transaction 如果 gtid_mode=ON 和 gtid_purged=ON|AUTO。The RELOAD or FLUSH_TABLES privilege is required with --single-transaction if both gtid_mode=ON and gtid_purged=ON|AUTO.

使用此选项时，您应该记住，只有 InnoDB 表会以一致状态转储。例如，使用此选项时转储的任何 MyISAM 或 MEMORY 表仍可能更改状态。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.

在--single-transaction导出过程中，为确保导出文件有效（表内容和二进制日志坐标正确），不应有其他连接使用以下语句：ALTER TABLE, CREATE TABLE, DROP TABLE, RENAME TABLE, TRUNCATE TABLE。一致性读并没有隔离这些语句，因此在要导出的表中使用它们可能会导致SELECT由mysqldump执行的表内容检索获取错误内容或失败。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 mysqldump to retrieve the table contents to obtain incorrect contents or fail.

--single-transaction 选项和 --lock-tables 选项是互斥的，因为 LOCK TABLES 会导致隐式提交任何挂起的事务。The --single-transaction option and the --lock-tables option are mutually exclusive because LOCK TABLES causes any pending transactions to be committed implicitly.

要转储大型表，请将 --single-transaction 选项与 --quick 选项。To dump large tables, combine the --single-transaction option with the --quick option.

--opt 选项可打开多个设置，这些设置协同工作以执行快速转储操作。默认情况下，所有这些设置均处于启用状态，因为 --opt 默认情况下处于启用状态。因此，您很少指定--opt。相反，您可以通过指定 --skip-opt 来整体关闭这些设置，然后通过稍后在命令行上指定关联选项来选择性地重新启用某些设置。The --opt option turns on several settings that work together to perform a fast dump operation. All of these settings are on by default, because --opt is on by default. Thus you rarely if ever specify --opt. Instead, you can turn these settings off as a group by specifying --skip-opt, then optionally re-enable certain settings by specifying the associated options later on the command line.

--compact 选项会关闭多个控制可选语句和注释是否出现在输出中的设置。同样，您可以在此选项后面加上其他选项来重新启用某些设置，或者使用 --skip-compact 表单打开所有设置。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 form.