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/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.0/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.0/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.0/en/replication-gtids-howto.html
If you are starting with new servers, see Section 19.1.2.3, “Creating a User for Replication” for information about adding a specific user for replication connections and Section 19.1.2.1, “Setting the Replication Source Configuration” for ... This section describes a process for configuring and starting GTID-based replication in MySQL ...
https://dev.mysql.com/doc/refman/8.0/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.0/en/replication-howto-slaveinit.html
To set up the replica to communicate with the source for replication, configure the replica with the necessary connection information. You must be able to connect to the source MySQL server using TCP/IP. The CHANGE REPLICATION SOURCE TO | CHANGE ...
https://dev.mysql.com/doc/refman/8.0/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.0/en/replication-multi-source-adding-gtid-master.html
These steps assume you have enabled GTIDs for transactions on the sources using gtid_mode=ON, created a replication user, ensured that the replica is using TABLE based replication applier metadata repositories, and provisioned the replica with data ...Use the CHANGE REPLICATION SOURCE TO statement (from MySQL 8.0.23) or CHANGE MASTER TO statement (before MySQL 8.0.23) to configure a replication channel for each source on the replica (see Section 19.2.2, “Replication ...
https://dev.mysql.com/doc/refman/8.0/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. MySQL multi-source replication enables a replica to receive transactions from multiple immediate sources in ...
https://dev.mysql.com/doc/refman/8.0/en/replication-options-reference.html
log_bin_trust_function_creators: If equal to 0 (default), then when --log-bin is used, stored function creation is allowed only to users having SUPER privilege and only if function created does not break binary logging. The following two sections ...