Search



Search Results
Displaying 1501 to 1510 of 4736 total results
https://dev.mysql.com/doc/refman/8.4/en/replication-channels.html
In MySQL multi-source replication, a replica opens multiple replication channels, one for each source server. The replication channels represent the path of transactions flowing from a source to the replica. Each replication channel has its own ...
https://dev.mysql.com/doc/refman/8.4/en/replication-compatibility.html
MySQL supports replication from an older source to a newer replica for version combinations where we support upgrades from the source version to the replica version as described at Section 1.3, “MySQL Releases: Innovation and LTS” and Section ...
https://dev.mysql.com/doc/refman/8.4/en/replication-delayed.html
MySQL supports delayed replication such that a replica server deliberately executes transactions later than the source by at least a specified amount of time. This section describes how to configure a replication delay on a replica, and how to ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-load-data.html
LOAD DATA is considered unsafe for statement-based logging (see Section 19.2.1.3, “Determination of Safe and Unsafe Statements in Binary Logging”). When binlog_format=MIXED is set, the statement is logged in row-based format. When ...
https://dev.mysql.com/doc/refman/8.4/en/replication-features-variables.html
sql_mode is also replicated except for the NO_DIR_IN_CREATE mode; the replica always preserves its own value for NO_DIR_IN_CREATE, regardless of changes to it on the source. However, when mysqlbinlog parses a SET @@sql_mode = mode statement, the ...
https://dev.mysql.com/doc/refman/8.4/en/replication-gtids-restrictions.html
Because GTID-based replication is dependent on transactions, some features otherwise available in MySQL are not supported when using it. This section provides information about restrictions on and limitations of replication with GTIDs. When using ...
https://dev.mysql.com/doc/refman/8.4/en/replication-howto-repuser.html
Each replica connects to the source using a MySQL user name and password, so there must be a user account on the source that the replica can use to connect. The user name is specified by the SOURCE_USER option of the CHANGE REPLICATION SOURCE TO ...
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 ...
https://dev.mysql.com/doc/refman/8.4/en/replication-multi-source-configuration.html
A multi-source replication topology requires at least two sources and one replica configured. In these tutorials, we assume that you have two sources source1 and source2, and a replica replicahost. The replica replicates one database from each of ...
https://dev.mysql.com/doc/refman/8.4/en/replication-options.html
The following sections contain information about mysqld options and server variables that are used in replication and for controlling the binary log. Options and variables for use on sources and replicas are covered separately, as are options and ...
Displaying 1501 to 1510 of 4736 total results