Mysql mac os dump

handerson / mysqlfix.sh

# MySQL Client

ln -s /Applications/MySQLWorkbench.app/Contents/Resources/mysql /usr/bin/mysql

# MySQL Dump

ln -s /Applications/MySQLWorkbench.app/Contents/Resources/mysqldump /usr/bin/mysqldump

# How to fix the «Library not loaded: libmysqlclient.18.dylib (LoadError)» error

sudo ln -s /usr/local/mysql/lib/libmysqlclient.18.dylib /usr/lib/libmysqlclient.18.dylib

This comment has been minimized.

Copy link Quote reply

steenzout commented Dec 8, 2014

This comment has been minimized.

Copy link Quote reply

jvillariaza commented Jan 19, 2015

This comment has been minimized.

Copy link Quote reply

thepaski commented Feb 24, 2015

also can be found @ /Applications/MySQLWorkbench.app/Contents/MacOS

This comment has been minimized.

Copy link Quote reply

ehsankhfr commented May 21, 2015

This comment has been minimized.

Copy link Quote reply

ryanooi commented Nov 30, 2015

This comment has been minimized.

Copy link Quote reply

totomz commented Feb 5, 2018

Updated to MySQLWorkbench 6.3 and newer osx

This comment has been minimized.

Copy link Quote reply

dieisonbeck commented Mar 8, 2019

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Как импортировать большой дамп базы MySQL в MAMP (Mac OS X)?

Если вы используете MAMP для разработки ваших PHP-проектов на локальном компьютере Mac, вам скорее всего необходимо импортировать большой дамп базы данных MySQL (более 32 мб) в ваше локальное окружение. Вы можете исправить максимальный размер файла для загрузки в файле php.ini, тем не менее если вес файла будет реально большим (более 100 мегабайт), операция может потребовать годы для выполнения команды.

В таком случае более удобно будет воспользоваться терминалом, тем более что скрипт занимает одну строку

Если вы только установили MAMP, то имейте ввиду, что по умолчанию пользователем базы данных является root (пароль: root). В итоге кусок необходимого кода для импорта становится таким:

/Applications/MAMP/Library/bin/mysql -u root -p

На Mac OS X вы можете просто перенести файл (способом drag-and-drop) в консолье и узнать полный путь до файла. По итогу Вам нужно сделать следующий шаги:

• Открыть приложение Терминал;
• Скопировать часть этой строчки /Applications/MAMP/Library/bin/mysql -u root -p;
• Теперь, перед тем как нажать «Enter», введите название базы данных и символ «
• Все! Команда готова! Нажмите «Enter» и немного подождите.

Прошу заметить что никакого сообщения об успешном выполнении импорта не выводится, поэтому вы увидете просто новую строку для выполнения новой команды. После этого перейдите в phpMyAdmin и проверьте заполнение данных.

При написании статьи были использованы материалы сайта Surgeworks .

Источник

Is it possible to install only mysqldump on macOS

Is it possible to install only mysqldump on macOS without MySQL itself.

I’m using MySQL db via Docker, but can’t dump the DB from my local machine via MySQL Workbench.

/Applications/MySQLWorkbench.app/Contents/MacOS/mysqldump is version 5.7.17, but the MySQL Server to be dumped has version 5.7.20.

Do you have any suggestions on how to fix that and be able to make dumps from my local machine.

4 Answers 4

Brew now also has package mysql-client , so you don’t need to install the full mysql package just in order to get tools like mysqldump ; It’s sufficient to run brew install mysql-client .

You should pay attention on the post-installation notice:

mysql-client is keg-only, which means it was not symlinked into /usr/local, because conflicts with mysql.

If you need to have mysql-client first in your PATH run:

echo ‘export PATH=»/usr/local/opt/mysql-client/bin:$PATH»‘ >>

Otherwise, you would need to use binary directly located at /usr/local/opt/mysql-client/bin/mysqldump .

/.bash_profile to reload it and put the changes in effect.

The latest mysql 5.7 can be installed via brew .

It takes up about 253MB + 19MB for openssl.

You can remove the server components and cruft manually to get the size down to 127MB

Brew doesn’t allow arbitrary package versions to be installed. Some packages do offer MINOR version installs like mysql@5.6 but you will get the latest from that series.

If you have previously installed a version though (and haven’t run brew cleanup ) it can be switched back to with brew switch .

On Linux, you should be able to install the mysql-client package (which includes mysqldump, mysql, mysqladmin, etc.) without the mysql-server. You’d have to install the mysql-shared package too.

But I don’t know of a package for MacOS that has these packages split up. The binary distribution for MacOS has everything.

You could install the MySQL package for MacOS and just ignore the fact that you have a mysqld instance. Or you could stop the instance and configure it not to start automatically at bootup (the MacOS distribution includes a System Preferences applet for MySQL, where you can configure it).

If you want just the client on MacOS, you’d probably have to download the source and build it yourself. I think that’s more trouble than it’s worth. It would require installing Xcode, and figuring out how to build the client only, etc. This work would likely take hours.

I’d just install the MacOS distribution and be done with the task.

Источник

Mysql mac os dump

The mysqldump client utility performs logical backups, producing a set of SQL statements that can be executed to reproduce the original database object definitions and table data. It dumps one or more MySQL databases for backup or transfer to another SQL server. The mysqldump command can also generate output in CSV, other delimited text, or XML format.

mysqldump requires at least the SELECT privilege for dumped tables, SHOW VIEW for dumped views, TRIGGER for dumped triggers, LOCK TABLES if the —single-transaction option is not used, and (as of MySQL 5.6.49) PROCESS if the —no-tablespaces option is not used. Certain options might require other privileges as noted in the option descriptions.

To reload a dump file, you must have the privileges required to execute the statements that it contains, such as the appropriate CREATE privileges for objects created by those statements.

mysqldump output can include ALTER DATABASE statements that change the database collation. These may be used when dumping stored programs to preserve their character encodings. To reload a dump file containing such statements, the ALTER privilege for the affected database is required.

A dump made using PowerShell on Windows with output redirection creates a file that has UTF-16 encoding:

However, UTF-16 is not permitted as a connection character set (see Impermissible Client Character Sets), so the dump file cannot be loaded correctly. To work around this issue, use the —result-file option, which creates the output in ASCII format:

Performance and Scalability Considerations

mysqldump advantages include the convenience and flexibility of viewing or even editing the output before restoring. You can clone databases for development and DBA work, or produce slight variations of an existing database for testing. It is not intended as a fast or scalable solution for backing up substantial amounts of data. With large data sizes, even if the backup step takes a reasonable time, restoring the data can be very slow because replaying the SQL statements involves disk I/O for insertion, index creation, and so on.

For large-scale backup and restore, a physical backup is more appropriate, to copy the data files in their original format that can be restored quickly:

If your tables are primarily InnoDB tables, or if you have a mix of InnoDB and MyISAM tables, consider using the mysqlbackup command of the MySQL Enterprise Backup product. (Available as part of the Enterprise subscription.) It provides the best performance for InnoDB backups with minimal disruption; it can also back up tables from MyISAM and other storage engines; and it provides a number of convenient options to accommodate different backup scenarios. See Section 24.2, “MySQL Enterprise Backup Overview”.

If your tables are primarily MyISAM tables, consider using the mysqlhotcopy instead, for better performance than mysqldump of backup and restore operations. See Section 4.6.10, “mysqlhotcopy — A Database Backup Program”.

mysqldump can retrieve and dump table contents row by row, or it can retrieve the entire content from a table and buffer it in memory before dumping it. Buffering in memory can be a problem if you are dumping large tables. To dump tables row by row, use the —quick option (or —opt , which enables —quick ). The —opt option (and hence —quick ) is enabled by default, so to enable memory buffering, use —skip-quick .

If you are using a recent version of mysqldump to generate a dump to be reloaded into a very old MySQL server, use the —skip-opt option instead of the —opt or —extended-insert option.

Invocation Syntax

There are in general three ways to use mysqldump —in order to dump a set of one or more tables, a set of one or more complete databases, or an entire MySQL server—as shown here:

To dump entire databases, do not name any tables following db_name , or use the —databases or —all-databases option.

To see a list of the options your version of mysqldump supports, issue the command mysqldump —help .

Option Syntax — Alphabetical Summary

mysqldump supports the following options, which can be specified on the command line or in the [mysqldump] and [client] groups of an option file. For information about option files used by MySQL programs, see Section 4.2.2.2, “Using Option Files”.

Table 4.13 mysqldump Options

Option Name	Description	Introduced
—add-drop-database	Add DROP DATABASE statement before each CREATE DATABASE statement
—add-drop-table	Add DROP TABLE statement before each CREATE TABLE statement
—add-drop-trigger	Add DROP TRIGGER statement before each CREATE TRIGGER statement
—add-locks	Surround each table dump with LOCK TABLES and UNLOCK TABLES statements
—all-databases	Dump all tables in all databases
—allow-keywords	Allow creation of column names that are keywords
—apply-slave-statements	Include STOP SLAVE prior to CHANGE MASTER statement and START SLAVE at end of output
—bind-address	Use specified network interface to connect to MySQL Server
—character-sets-dir	Directory where character sets are installed
—comments	Add comments to dump file
—compact	Produce more compact output
—compatible	Produce output that is more compatible with other database systems or with older MySQL servers
—complete-insert	Use complete INSERT statements that include column names
—compress	Compress all information sent between client and server
—create-options	Include all MySQL-specific table options in CREATE TABLE statements
—databases	Interpret all name arguments as database names
—debug	Write debugging log
—debug-check	Print debugging information when program exits
—debug-info	Print debugging information, memory, and CPU statistics when program exits
—default-auth	Authentication plugin to use
—default-character-set	Specify default character set
—defaults-extra-file	Read named option file in addition to usual option files
—defaults-file	Read only named option file
—defaults-group-suffix	Option group suffix value
—delayed-insert	Write INSERT DELAYED statements rather than INSERT statements
—delete-master-logs	On a replication source server, delete the binary logs after performing the dump operation
—disable-keys	For each table, surround INSERT statements with statements to disable and enable keys
—dump-date	Include dump date as «Dump completed on» comment if —comments is given
—dump-slave	Include CHANGE MASTER statement that lists binary log coordinates of replica’s source
—enable-cleartext-plugin	Enable cleartext authentication plugin	5.6.28
—events	Dump events from dumped databases
—extended-insert	Use multiple-row INSERT syntax
—fields-enclosed-by	This option is used with the —tab option and has the same meaning as the corresponding clause for LOAD DATA
—fields-escaped-by	This option is used with the —tab option and has the same meaning as the corresponding clause for LOAD DATA
—fields-optionally-enclosed-by	This option is used with the —tab option and has the same meaning as the corresponding clause for LOAD DATA
—fields-terminated-by	This option is used with the —tab option and has the same meaning as the corresponding clause for LOAD DATA
—flush-logs	Flush MySQL server log files before starting dump
—flush-privileges	Emit a FLUSH PRIVILEGES statement after dumping mysql database
—force	Continue even if an SQL error occurs during a table dump
—help	Display help message and exit
—hex-blob	Dump binary columns using hexadecimal notation
—host	Host on which MySQL server is located
—ignore-table	Do not dump given table
—include-master-host-port	Include MASTER_HOST/MASTER_PORT options in CHANGE MASTER statement produced with —dump-slave
—insert-ignore	Write INSERT IGNORE rather than INSERT statements
—lines-terminated-by	This option is used with the —tab option and has the same meaning as the corresponding clause for LOAD DATA
—lock-all-tables	Lock all tables across all databases
—lock-tables	Lock all tables before dumping them
—log-error	Append warnings and errors to named file
—login-path	Read login path options from .mylogin.cnf
—master-data	Write the binary log file name and position to the output
—max-allowed-packet	Maximum packet length to send to or receive from server
—net-buffer-length	Buffer size for TCP/IP and socket communication
—no-autocommit	Enclose the INSERT statements for each dumped table within SET autocommit = 0 and COMMIT statements
—no-create-db	Do not write CREATE DATABASE statements
—no-create-info	Do not write CREATE TABLE statements that re-create each dumped table
—no-data	Do not dump table contents
—no-defaults	Read no option files
—no-set-names	Same as —skip-set-charset
—no-tablespaces	Do not write any CREATE LOGFILE GROUP or CREATE TABLESPACE statements in output
—opt	Shorthand for —add-drop-table —add-locks —create-options —disable-keys —extended-insert —lock-tables —quick —set-charset
—order-by-primary	Dump each table’s rows sorted by its primary key, or by its first unique index
—password	Password to use when connecting to server
—pipe	Connect to server using named pipe (Windows only)
—plugin-dir	Directory where plugins are installed
—port	TCP/IP port number for connection
—print-defaults	Print default options
—protocol	Transport protocol to use
—quick	Retrieve rows for a table from the server a row at a time
—quote-names	Quote identifiers within backtick characters
—replace	Write REPLACE statements rather than INSERT statements
—result-file	Direct output to a given file
—routines	Dump stored routines (procedures and functions) from dumped databases
—secure-auth	Do not send passwords to server in old (pre-4.1) format	5.6.17
—set-charset	Add SET NAMES default_character_set to output
—set-gtid-purged	Whether to add SET @@GLOBAL.GTID_PURGED to output
—shared-memory-base-name	Shared-memory name for shared-memory connections (Windows only)
—single-transaction	Issue a BEGIN SQL statement before dumping data from server
—skip-add-drop-table	Do not add a DROP TABLE statement before each CREATE TABLE statement
—skip-add-locks	Do not add locks
—skip-comments	Do not add comments to dump file
—skip-compact	Do not produce more compact output
—skip-disable-keys	Do not disable keys
—skip-extended-insert	Turn off extended-insert
—skip-opt	Turn off options set by —opt
—skip-quick	Do not retrieve rows for a table from the server a row at a time
—skip-quote-names	Do not quote identifiers
—skip-set-charset	Do not write SET NAMES statement
—skip-triggers	Do not dump triggers
—skip-tz-utc	Turn off tz-utc
—socket	Unix socket file or Windows named pipe to use
—ssl	Enable connection encryption
—ssl-ca	File that contains list of trusted SSL Certificate Authorities
—ssl-capath	Directory that contains trusted SSL Certificate Authority certificate files
—ssl-cert	File that contains X.509 certificate
—ssl-cipher	Permissible ciphers for connection encryption
—ssl-crl	File that contains certificate revocation lists
—ssl-crlpath	Directory that contains certificate revocation-list files
—ssl-key	File that contains X.509 key
—ssl-mode	Desired security state of connection to server	5.6.30
—ssl-verify-server-cert	Verify host name against server certificate Common Name identity
—tab	Produce tab-separated data files
—tables	Override —databases or -B option
—triggers	Dump triggers for each dumped table
—tz-utc	Add SET TIME_ZONE=’+00:00′ to dump file
—user	MySQL user name to use when connecting to server
—verbose	Verbose mode
—version	Display version information and exit
—where	Dump only rows selected by given WHERE condition
—xml	Produce XML output

Connection Options

The mysqldump command logs into a MySQL server to extract information. The following options specify how to connect to the MySQL server, either on the same machine or a remote system.

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

Compress all information sent between the client and the server if possible. See Section 4.2.6, “Connection Compression Control”.

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

Enable the mysql_clear_password cleartext authentication plugin. (See Section 6.4.1.5, “Client-Side Cleartext Pluggable Authentication”.)

This option was added in MySQL 5.6.28.

—host= host_name , -h host_name

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

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 4.6.6, “mysql_config_editor — MySQL Configuration Utility”.

For additional information about this and other option-file options, see Section 4.2.2.3, “Command-Line Options that Affect Option-File Handling”.

—password[= password ] , -p[ password ]

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.

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

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.

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 6.2.11, “Pluggable Authentication”.

—port= port_num , -P port_num

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

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 4.2.5, “Connection Transport Protocols”.

Do not send passwords to the server in old (pre-4.1) format. This prevents connections except for servers that use the newer password format. This option is enabled by default; use —skip-secure-auth to disable it. This option was added in MySQL 5.6.17.

Passwords that use the pre-4.1 hashing method are less secure than passwords that use the native password hashing method and should be avoided. Pre-4.1 passwords are deprecated; expect support for them to be removed in a future MySQL release. For account upgrade instructions, see Section 6.4.1.3, “Migrating Away from Pre-4.1 Password Hashing and the mysql_old_password Plugin”.

This option is deprecated; expect it to be removed in a future release. As of MySQL 5.7.5, it is always enabled and attempting to disable it produces an error.

—socket= path , -S path

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

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.

—user= user_name , -u user_name

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

Option-File Options

These options are used to control which option files to read.

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.

For additional information about this and other option-file options, see Section 4.2.2.3, “Command-Line Options that Affect Option-File Handling”.

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.

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 Affect Option-File Handling”.

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.

For additional information about this and other option-file options, see Section 4.2.2.3, “Command-Line Options that Affect Option-File Handling”.

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.

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 4.6.6, “mysql_config_editor — MySQL Configuration Utility”.

For additional information about this and other option-file options, see Section 4.2.2.3, “Command-Line Options that Affect Option-File Handling”.

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 Affect Option-File Handling”.

DDL Options

Usage scenarios for mysqldump include setting up an entire new MySQL instance (including database tables), and replacing data inside an existing instance with existing databases and tables. The following options let you specify which things to tear down and set up when restoring a dump, by encoding various DDL statements within the dump file.

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.

Write a DROP TABLE statement before each CREATE TABLE statement.

Write a DROP TRIGGER statement before each CREATE TRIGGER statement.

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.

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

Do not write CREATE TABLE statements that create each dumped table.

This option does not exclude statements creating log file groups or tablespaces from mysqldump output; however, you can use the —no-tablespaces option for this purpose.

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

Write REPLACE statements rather than INSERT statements.

Debug Options

The following options print debugging information, encode debugging information in the dump file, or let the dump operation proceed regardless of potential problems.

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

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 ]

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 .

This option is available only if MySQL was built using WITH_DEBUG . MySQL release binaries provided by Oracle are not built using this option.

Print some debugging information when the program exits.

This option is available only if MySQL was built using WITH_DEBUG . MySQL release binaries provided by Oracle are not built using this option.

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

This option is available only if MySQL was built using WITH_DEBUG . MySQL release binaries provided by Oracle are not built using this option.

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. —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.

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

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

See the description for the —comments option.

Verbose mode. Print more information about what the program does.

Help Options

The following options display information about the mysqldump command itself.

Display a help message and exit.

Display version information and exit.

Internationalization Options

The following options change how the mysqldump command represents character data with national language settings.

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

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

Turns off the —set-charset setting, the same as specifying —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 .

Replication Options

The mysqldump command is frequently used to create an empty instance, or an instance including data, on a replica server in a replication configuration. The following options apply to dumping and restoring data on replication source and replica servers.

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

On a source replication server, delete the binary logs by sending a PURGE BINARY LOGS statement to the server after performing the dump operation. This option requires the RELOAD privilege as well as privileges sufficient to execute that statement. This option automatically enables —master-data .

This option is similar to —master-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. It causes the dump output to include a CHANGE MASTER TO statement that indicates the binary log coordinates (file name and position) of the dumped replica’s source. These are the source server coordinates from which the replica should start replicating.

—dump-slave causes the coordinates from the source to be used rather than those of the dumped server, as is done by the —master-data option. In addition, specifiying this option causes the —master-data option to be overridden, if used, and effectively ignored.

The option value is handled the same way as for —master-data (setting no value or 1 causes a CHANGE MASTER TO statement to be written to the dump, setting 2 causes the statement to be written but encased in SQL comments) and has the same effect as —master-data in terms of enabling or disabling other options and in how locking is handled.

This option causes mysqldump to stop the replica SQL thread before the dump and restart it again after.

—dump-slave sends a SHOW SLAVE STATUS statement to the server to obtain information, so it requires privileges sufficient to execute that statement.

In conjunction with —dump-slave , the —apply-slave-statements and —include-master-host-port options can also be used.

For the CHANGE MASTER TO statement in a replica dump produced with the —dump-slave option, add MASTER_HOST and MASTER_PORT options for the host name and TCP/IP port number of the replica’s source.

Use this option to dump a source replication server to produce a dump file that can be used to set up another server as a replica of the source. It causes the dump output to include a CHANGE MASTER TO statement that indicates the binary log coordinates (file name and position) of the dumped server. These are the source server coordinates from which the replica should start replicating after you load the dump file into the replica.

If the option value is 2, the CHANGE MASTER 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.

—master-data sends a SHOW MASTER STATUS statement to the server to obtain information, so it requires privileges sufficient to execute that statement. This option also 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-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.

It is also possible to set up a replica by dumping an existing replica of the source, using the —dump-slave option, which overrides —master-data and causes it to be ignored if both options are used.

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

The following table shows the permitted option values. The default value is AUTO .

Value	Meaning
OFF	Add no SET statement to the output.
ON	Add a SET statement to the output. An error occurs if GTIDs are not enabled on the server.
AUTO	Add a SET statement to the output if GTIDs are enabled on the server.

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

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

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

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

It is not recommended to load a dump file when GTIDs are enabled on the server ( gtid_mode=ON ), if your dump file includes system tables. mysqldump issues DML instructions for the system tables which use the non-transactional MyISAM storage engine, and this combination is not permitted when GTIDs are enabled. Also be aware that loading a dump file from a server with GTIDs enabled, into another server with GTIDs enabled, causes different transaction identifiers to be generated.

Format Options

The following options specify how to represent the entire dump file or certain kinds of data in the dump file. They also control whether certain optional information is written to the dump file.

Produce output that is more compatible with other database systems or with older MySQL servers. The value of name can be ansi , mysql323 , mysql40 , postgresql , oracle , mssql , db2 , maxdb , no_key_options , no_table_options , or no_field_options . To use several values, separate them by commas. These values have the same meaning as the corresponding options for setting the server SQL mode. See Section 5.1.10, “Server SQL Modes”.

This option does not guarantee compatibility with other servers. It only enables those SQL mode values that are currently available for making dump output more compatible. For example, —compatible=oracle does not map data types to Oracle types or use Oracle comment syntax.

Use complete INSERT statements that include column names.

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

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

These options are used with the —tab option and have the same meaning as the corresponding FIELDS clauses for LOAD DATA . See Section 13.2.6, “LOAD DATA Statement”.

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.

This option is used with the —tab option and has the same meaning as the corresponding LINES clause for LOAD DATA . See Section 13.2.6, “LOAD DATA Statement”.

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

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.

This option should be used on Windows to prevent newline \n characters from being converted to \r\n carriage return/newline sequences.

—tab= dir_name , -T dir_name

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.

This 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 you use must have the FILE privilege. Because mysqldump creates *.sql in the same directory, it must be writable by your system login 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.

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 .

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’ are distinguished from one another in the output generated by this option as follows.

The output from the mysql client when run using the —xml option also follows the preceding rules. (See Section 4.5.1.1, “mysql Client Options”.)

XML output from mysqldump includes the XML namespace, as shown here:

Filtering Options

The following options control which kinds of schema objects are written to the dump file: by category, such as triggers or events; by name, for example, choosing which databases and tables to dump; or even filtering rows from the table data using a WHERE clause.

Dump all tables in all databases. This is the same as using the —databases option and naming all the databases on the command line.

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.

This option may be used to dump the INFORMATION_SCHEMA and performance_schema databases, which normally are not dumped even with the —all-databases option. (Also use the —skip-lock-tables option.)

Include Event Scheduler events for the dumped databases in the output. This option requires the EVENT privileges for those databases.

The output generated by using —events contains CREATE EVENT statements to create the events. However, these statements do not include attributes such as the event creation and modification timestamps, so when the events are reloaded, they are created with timestamps equal to the reload time.

If you require events to be created with their original timestamp attributes, do not use —events . Instead, dump and reload the contents of the mysql.event table directly, using a MySQL account that has appropriate privileges for the mysql database.

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.

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).

Include stored routines (procedures and functions) for the dumped databases in the output. This option requires the SELECT privilege for the mysql.proc table.

The output generated by using —routines contains CREATE PROCEDURE and CREATE FUNCTION statements to create the routines. However, these statements do not include attributes such as the routine creation and modification timestamps, so when the routines are reloaded, they are created with timestamps equal to the reload time.

If you require routines to be created with their original timestamp attributes, do not use —routines . Instead, dump and reload the contents of the mysql.proc table directly, using a MySQL account that has appropriate privileges for the mysql database.

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

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.

—where=’ where_condition ‘ , -w ‘ where_condition ‘

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.

Performance Options

The following options are the most relevant for the performance particularly of the restore operations. For large data sets, restore operation (processing the INSERT statements in the dump file) is the most time-consuming part. When it is urgent to restore data quickly, plan and test the performance of this stage in advance. For restore times measured in hours, you might prefer an alternative backup and restore solution, such as MySQL Enterprise Backup for InnoDB -only and mixed-use databases, or mysqlhotcopy for MyISAM -only databases.

Performance is also affected by the transactional options, primarily for the dump operation.

For those nontransactional tables that support the INSERT DELAYED syntax, use that statement rather than regular INSERT statements.

As of MySQL 5.6.6, DELAYED inserts are deprecated; expect this option to be removed in a future release.

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.

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.

Write INSERT IGNORE statements rather than INSERT statements.

The maximum size of the buffer for client/server communication. The default is 24MB, the maximum is 1GB.

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.

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.

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 .

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

See the description for the —opt option.

Transactional Options

The following options trade off the performance of the dump operation, against the reliability and consistency of the exported data.

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

Flush the MySQL server log files before starting the dump. This option requires the RELOAD privilege. If you use this option in combination with the —all-databases option, the logs are flushed for each database dumped . The exception is when using —lock-all-tables , —master-data , or —single-transaction : In this case, the logs are flushed only once, corresponding to the moment that all tables are locked by FLUSH TABLES WITH READ LOCK . If you want your dump and the log flush to happen at exactly the same moment, you should use —flush-logs together with —lock-all-tables , —master-data , or —single-transaction .

Add a FLUSH PRIVILEGES statement to the dump output after dumping the mysql database. This option should be used any time the dump contains the mysql database and any other database that depends on the data in the mysql database for proper restoration.

Because the dump file contains a FLUSH PRIVILEGES statement, reloading the file requires privileges sufficient to execute that statement.

Lock all tables across all databases. This is achieved by acquiring a global read lock for the duration of the whole dump. This option automatically turns off —single-transaction and —lock-tables .

For each dumped database, lock all tables to be dumped before dumping them. The tables are locked with READ LOCAL to permit concurrent inserts in the case of MyISAM tables. For transactional tables such as InnoDB , —single-transaction is a much better option than —lock-tables because it does not need to lock the tables at all.

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.

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.

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

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.

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-memory connections.

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

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

While a —single-transaction dump is in process, to ensure a valid dump file (correct table contents and binary log coordinates), no other connection should use the following statements: ALTER TABLE , CREATE TABLE , DROP TABLE , RENAME TABLE , TRUNCATE TABLE . A consistent read is not isolated from those statements, so use of them on a table to be dumped can cause the SELECT that is performed by 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 pending transactions 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 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 , the optionally re-enable certain settings by specifying the associated options later on the command 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 form.

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

To make a backup of an entire database:

To load the dump file back into the server:

Another way to reload the dump file:

mysqldump is also very useful for populating databases by copying data from one MySQL server to another:

You can dump several databases with one command:

To dump all databases, use the —all-databases option:

For InnoDB tables, mysqldump provides a way of making an online backup:

This backup acquires a global read lock on all tables (using FLUSH TABLES WITH READ LOCK ) at the beginning of the dump. As soon as this lock has been acquired, the binary log coordinates are read and the lock is released. If long updating statements are running when the FLUSH statement is issued, the MySQL server may get stalled until those statements finish. After that, the dump becomes lock free and does not disturb reads and writes on the tables. If the update statements that the MySQL server receives are short (in terms of 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 happened since 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 log coordinates to which the dump corresponds:

The —master-data and —single-transaction options can be used simultaneously, which provides a convenient way to make an online backup suitable for use prior to point-in-time recovery if tables are stored using the InnoDB storage engine.

To select the effect of —opt except for some features, use the —skip option for each feature. To disable extended inserts and memory buffering, use —opt —skip-extended-insert —skip-quick . (Actually, —skip-extended-insert —skip-quick is sufficient because —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

mysqldump does not dump the INFORMATION_SCHEMA or performance_schema database by default. To dump either of these, name it explicitly on the command line. You can also name it with the —databases option. Also, use the —skip-lock-tables option.

mysqldump does not dump the NDB Cluster ndbinfo information database.

If you encounter problems backing up views due to insufficient privileges, see Section 20.9, “Restrictions on Views” for a workaround.

Источник

Value:	XML Representation:
NULL ( unknown value )