Search Results
https://dev.mysql.com/doc/refman/8.4/en/repeat.html
[begin_label:] REPEAT statement_list UNTIL search_condition END REPEAT [end_label] The statement list within a REPEAT statement is repeated until the search_condition expression is true. statement_list consists of one or more statements, each ...
https://dev.mysql.com/doc/refman/8.4/en/replica-io-thread-states.html
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 also appears in the Replica_IO_State column displayed by SHOW REPLICA STATUS, so you can get a good ...
https://dev.mysql.com/doc/refman/8.4/en/replica-sql-thread-states.html
The following list shows the most common states you may see in the State column for a replication SQL thread on a replica server. Monitoring tools that work with these instrumentation names might be impacted. If the incompatible changes have an ...
https://dev.mysql.com/doc/refman/8.4/en/replication-asynchronous-connection-failover.html
You can use the asynchronous connection failover mechanism to establish an asynchronous (source-to-replica) replication connection to a new source automatically, after the existing connection from a replica to its source fails. The asynchronous ...
https://dev.mysql.com/doc/refman/8.4/en/replication-binlog-encryption-encryption-keys.html
The binary log encryption keys used to encrypt the file passwords for the log files are 256-bit keys that are generated specifically for each MySQL server instance using MySQL Server's keyring service (see Section 8.4.4, “The MySQL Keyring”).
https://dev.mysql.com/doc/refman/8.4/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.4/en/replication-configuration.html
This section describes how to configure the different types of replication available in MySQL and includes the setup and configuration required for a replication environment, including step-by-step instructions for creating a new replication ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-create-select.html
SELECT always performs an implicit commit (Section 15.3.3, “Statements That Cause an Implicit Commit”). If the destination table does not exist, logging occurs as follows. ROW format: The statement is logged as a CREATE TABLE statement followed ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-directory.html
If a DATA DIRECTORY or INDEX DIRECTORY table option is used in a CREATE TABLE statement on the source server, the table option is also used on the replica. This can cause problems if no corresponding directory exists in the replica host file system ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-errors.html
If a statement produces the same error (identical error code) on both the source and the replica, the error is logged, but replication continues. If a statement produces different errors on the source and the replica, the replication SQL thread ...