PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 297.2Kb
Man Pages (Zip)
- 402.4Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/reloading-delimited-text-dumps.html
For backups produced with mysqldump --tab, each table is represented in the output directory by an .sql file containing the CREATE TABLE statement for the table, and a .txt file containing the table data. To reload a table, first change location ...
https://dev.mysql.com/doc/refman/8.0/en/rename-user.html
To use RENAME USER, you must have the global CREATE USER privilege, or the UPDATE privilege for the mysql system schema. However, RENAME USER does not automatically drop or invalidate databases or objects within them that the old user created.
https://dev.mysql.com/doc/refman/8.0/en/replica-logs.html
A replica server creates several repositories of information to use for the replication process: The replica's relay log, which is written by the replication I/O (receiver) thread, contains the transactions read from the replication source server's ...The transactions in the relay log are applied on the replica by the replication SQL (applier) ...
https://dev.mysql.com/doc/refman/8.0/en/replica-sql-thread-states.html
Making temporary file (create) before replaying LOAD DATA INFILE The thread is executing a LOAD DATA statement and is creating a temporary file containing the data from which the replica reads rows. The following list shows the most common states ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption-scope.html
Note If you use LOAD DATA when binlog_format=STATEMENT is set, which is not recommended as the statement is considered unsafe for statement-based replication, a temporary file containing the data is created on the replica where the changes are ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-charset.html
The following applies to replication between MySQL servers that use different character sets: If the source has databases with a character set different from the global character_set_server value, you should design your CREATE TABLE statements so ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-masterstatus.html
If you are planning to shut down the source to create a data snapshot, you can optionally skip this procedure and instead store a copy of the binary log index file along with the data snapshot. In that situation, the source creates a new binary log ... To configure the replica to start the replication process at the correct point, you need to note the source's current coordinates within its binary ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rules-channel-based-filters.html
The syntax to create channel specific replication filters extends the existing SQL statements and command options. The default replication channel is the replication channel which always exists once replication has been started, and differs from ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rules-db-options.html
Important For statement-based logging, an exception is made in the rules just given for the CREATE DATABASE, ALTER DATABASE, and DROP DATABASE statements. In those cases, the database being created, altered, or dropped replaces the default database ... When evaluating replication options, the replica begins by checking to see whether there are any --replicate-do-db or --replicate-ignore-db options that ...
https://dev.mysql.com/doc/refman/8.0/en/replication-rules.html
The rules governing such filters are the same whether they are created on startup using --replicate-* options or while the replica server is running by CHANGE REPLICATION FILTER. For statements affecting databases only (that is, CREATE DATABASE, ...