Search Results
https://dev.mysql.com/doc/refman/8.4/en/replication-features-memory.html
A change in max_heap_table_size takes effect for MEMORY tables that are created or updated using ALTER TABLE ... When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate this effect to replicas, the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-partitioning.html
To avoid stopping replication or creating inconsistencies between the source and replica, always ensure that a table on the source and the corresponding replicated table on the replica are partitioned in the same way. Replication is supported ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-row-searches.html
The algorithm creates a hash table containing the rows in the UPDATE or DELETE operation, with the key as the full before-image of the row. When a replica using row-based replication format applies an UPDATE or DELETE operation, it must search the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-temptables.html
In statement-based replication mode, CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE statements cannot be used inside a transaction, procedure, function, or trigger when GTIDs are in use on the server (that is, when the enforce_gtid_consistency ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-auto-positioning.html
The correct approach to recover from this situation is for the replica to replicate the missing transactions listed in the ER_FOUND_MISSING_GTIDS message from another source, or for the replica to be replaced by a new replica created from a more ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids.html
This section discusses the following topics: How GTIDs are defined and created, and how they are represented in a MySQL server (see Section 19.1.3.1, “GTID Format and Storage”). This section explains transaction-based replication using global ...
https://dev.mysql.com/doc/refman/8.4/en/replication-implementation.html
Tables are created or their structure modified, and data is inserted, deleted, and updated according to the changes that were originally made on the source. Replication is based on the source server keeping track of all changes to its databases ...
https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source.html
In a multi-source replication topology, a replica creates a replication channel for each source that it should receive transactions from. Multi-source replication in MySQL 8.4 enables a replica to receive transactions from multiple immediate ...
https://dev.mysql.com/doc/refman/8.4/en/replication-privilege-checks-gr.html
For example: mysql> STOP GROUP_REPLICATION; mysql> CHANGE REPLICATION SOURCE TO PRIVILEGE_CHECKS_USER = 'gr_repl'@'%.example.com' FOR CHANNEL 'group_replication_recovery'; mysql> FLUSH PRIVILEGES; mysql> START GROUP_REPLICATION; For Group ... You ...
https://dev.mysql.com/doc/refman/8.4/en/replication-solutions-backups.html
Using the raw data files option also means that you can back up the binary and relay logs that make it possible to re-create the replica in the event of a replica failure. To use replication as a backup solution, replicate data from the source to a ...