PDF (US Ltr)
- 43.3Mb
PDF (A4)
- 43.4Mb
Man Pages (TGZ)
- 296.6Kb
Man Pages (Zip)
- 402.0Kb
Info (Gzip)
- 4.3Mb
Info (Zip)
- 4.3Mb
Search Results
https://dev.mysql.com/doc/refman/8.0/en/rename-table.html
Foreign key constraint names that point to the renamed table are automatically updated unless there is a conflict, in which case the statement fails with an error. RENAME TABLE tbl_name TO new_tbl_name [, tbl_name2 TO new_tbl_name2] ... You must ...
https://dev.mysql.com/doc/refman/8.0/en/replica-io-thread-states.html
At that point, the thread considers the connection to be broken and makes an attempt to reconnect. The following list shows the most common states you see in the State column for a replication I/O (receiver) thread on a replica server. This state ...
https://dev.mysql.com/doc/refman/8.0/en/replica-logs-status.html
A replica server creates two replication metadata repositories, the connection metadata repository and the applier metadata repository. If binary log file position based replication is in use, when the replica restarts, it reads the two ...
https://dev.mysql.com/doc/refman/8.0/en/replication-binlog-encryption-scope.html
Existing binary log files and relay log files that were present on the server when you started encryption are not encrypted. You can purge these files when they are no longer needed. Data in motion in the replication event stream, which is sent to ...
https://dev.mysql.com/doc/refman/8.0/en/replication-features-transaction-inconsistencies.html
That is, all transactions up to point N have been applied, and no transactions after N have been applied, but Exec_master_log_pos has a value smaller than N. Inconsistencies in the sequence of transactions that have been executed from the relay log ...
https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-auto-positioning.html
GTIDs replace the file-offset pairs previously required to determine points for starting, stopping, or resuming the flow of data between source and replica. When GTIDs are in use, all the information that the replica needs for synchronizing with ...
https://dev.mysql.com/doc/refman/8.0/en/replication-howto-masterstatus.html
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 log. Warning This procedure uses FLUSH TABLES WITH READ LOCK, which blocks COMMIT operations for ...
https://dev.mysql.com/doc/refman/8.0/en/replication-privilege-checks-recover.html
For instructions to do this, see Section 9.5, “Point-in-Time (Incremental) Recovery”. If a privilege check against the PRIVILEGE_CHECKS_USER account fails, the transaction is not executed and replication stops for the channel. Details of the ...
https://dev.mysql.com/doc/refman/8.0/en/replication-privilege-checks.html
When you restart the replication channel, checks on dynamic privileges are applied from that point on. By default, MySQL replication (including Group Replication) does not carry out privilege checks when transactions that were already accepted by ...
https://dev.mysql.com/doc/refman/8.0/en/replication-semisync-interface.html
The rpl_semi_sync_source_wait_point or rpl_semi_sync_master_wait_point system variable controls the point at which a semisynchronous source server waits for replica acknowledgment of transaction receipt before returning a status to the client that ... When you install the source and replica plugins for semisynchronous replication (see Section 19.4.10.1, “Installing Semisynchronous Replication”), system variables become available to control plugin ...