PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.6Kb
Man Pages (Zip)
- 401.9Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/replication-threads.html
MySQL replication capabilities are implemented using the following types of threads: Binary log dump thread. This thread can be identified in the output of SHOW PROCESSLIST on the source as the Binlog Dump thread. The replication receiver thread ...
https://dev.mysql.com/doc/refman/8.0/en/select-into.html
INTO DUMPFILE writes a single row to a file without any formatting. INTO OUTFILE statement is intended to enable dumping a table to a text file on the server host. If no such clause is present, values are dumped using the binary character set. INTO ...INTO form of SELECT enables a query result to be stored in variables or written to a file: SELECT ...
https://dev.mysql.com/doc/refman/8.0/en/set-sql-log-bin.html
mysqldump adds a SET @@SESSION.sql_log_bin=0 statement to a dump file from a server where GTIDs are in use, which disables binary logging while the dump file is being reloaded. The statement prevents new GTIDs from being generated and assigned to ...
https://dev.mysql.com/doc/refman/8.0/en/sql-mode.html
(Storing 0 is not a recommended practice, by the way.) For example, if you dump the table with mysqldump and then reload it, MySQL normally generates new sequence numbers when it encounters the 0 values, resulting in a table with contents different ... The MySQL server can operate in different SQL modes, and can apply these modes differently for different clients, depending on the value of the sql_mode system ...
https://dev.mysql.com/doc/refman/8.0/en/sys-schema-usage.html
To generate a dump file, name the sys schema explicitly on the command line using either of these commands: mysqldump --databases --routines sys > sys_dump.sql mysqlpump sys > sys_dump.sql To reinstall the schema from the dump file, use this ...Most ...
https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html
Loading a dump file that includes the NO_AUTO_CREATE_USER SQL mode in stored program definitions into a MySQL 8.0 server causes a failure. As of MySQL 5.7.24 and MySQL 8.0.13, mysqldump removes NO_AUTO_CREATE_USER from stored program definitions.
https://dev.mysql.com/doc/refman/8.0/en/zlib-decompress.html
Invoke zlib_decompress like this: zlib_decompress input_file output_file Example: mysqlpump --compress-output=ZLIB > dump.zlib zlib_decompress dump.zlib dump.txt To see a help message, invoke zlib_decompress with no arguments. The zlib_decompress ...
https://dev.mysql.com/doc/refman/8.0/en/backup-types.html
Logical backup tools include the mysqldump program and the SELECT ... To restore logical backups, SQL-format dump files can be processed using the mysql client. For SQL output (CREATE and INSERT statements), local or remote dumps can be done and ...
https://dev.mysql.com/doc/refman/8.0/en/bug-reports.html
If you cannot produce a test case with only a few rows, or if the test table is too big to be included in the bug report (more than 10 rows), you should dump your tables using mysqldump and create a README file that describes your problem. If data ... Before posting a bug report about a problem, please try to verify that it is a bug and that it has not been reported already: Start by searching the MySQL online manual at ...
https://dev.mysql.com/doc/refman/8.0/en/ddl-rewriter-installation.html
The primary use case is modification of statements restored from dump files, so the typical usage pattern is: 1) Install the plugin; 2) restore the dump file or files; 3) uninstall the plugin. This section describes how to install or uninstall the ...