Search



Search Results
Displaying 3191 to 3200 of 3292 total results
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-functions.html
The function can return the union of gtid_executed on each replica with the set of transactions received by the replica, which is recorded in the Performance Schema replication_connection_status table. This section provides examples of stored ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-howto.html
It is not mandatory to have binary logging enabled in order to use GTIDs when using the mysql.gtid_executed Table. This section describes a process for configuring and starting GTID-based replication in MySQL 8.4. This is a “cold start” ...
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-adding-binlog-master.html
These steps assume that binary logging is enabled on the source (which is the default), the replica is using TABLE based replication applier metadata repositories (which is the default in MySQL 8.4), and that you have enabled a replication user and ...Use a CHANGE REPLICATION SOURCE TO statement to configure a replication channel for each source on the replica (see Section 19.2.2, “Replication ...
https://dev.mysql.com/doc/refman/8.4/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 CHANGE REPLICATION SOURCE TO to configure a replication channel for each source on the replica (see Section 19.2.2, “Replication ...
https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source-configuration.html
Replicas in a multi-source replication topology require TABLE repositories for the replica's connection metadata repository and applier metadata repository, which are the default in MySQL 8.4. Create a suitable user account on all the sources that ... A multi-source replication topology requires at least two sources and one replica ...
https://dev.mysql.com/doc/refman/8.4/en/replication-privilege-checks-gr.html
Group Replication requires every table that is to be replicated by the group to have a defined primary key, or primary key equivalent where the equivalent is a non-null unique key. You may set the REQUIRE_TABLE_PRIMARY_KEY_CHECK option of the CHANGE ... You can also use a PRIVILEGE_CHECKS_USER account to secure the two replication applier threads used by Group ...
https://dev.mysql.com/doc/refman/8.4/en/replication-semisync-installation.html
To verify plugin installation, examine the Information Schema PLUGINS table or use the SHOW PLUGINS statement (see Section 7.6.2, “Obtaining Server Plugin Information”). Semisynchronous replication is implemented using plugins, which must be ...
https://dev.mysql.com/doc/refman/8.4/en/replication-threads-monitor-worker.html
On a multithreaded replica, the Performance Schema tables replication_applier_status_by_coordinator and replication_applier_status_by_worker show status information for the replica's coordinator thread and applier worker threads respectively. For a ...
https://dev.mysql.com/doc/refman/8.4/en/replication.html
Depending on the configuration, you can replicate all databases, selected databases, or even selected tables within a database. Replication enables data from one MySQL database server (known as a source) to be copied to one or more MySQL database ...
Displaying 3191 to 3200 of 3292 total results