Replication Master Options and Variables This section describes the server options and system variables that you can use on replication master servers. You can specify the options either on the command line or in an option file. You can specify system variable values using SET. On the master and...
Replication of Columns Having Different Data Types Corresponding columns on the master's and the slave's copies of the same table ideally should have the same data type. However, beginning with MySQL 5.1.21, this is not always strictly enforced, as long as certain conditions are met. All other t...
Replication of CREATE TABLE ... SELECT Statements This section discusses how MySQL replicates CREATE TABLE ... SELECT statements. MySQL 5.6 does not allow a CREATE TABLE ... SELECT statement to make any changes in tables other than the table that...
Replication of CURRENT_USER() The following statements support use of the CURRENT_USER() [1287] function to take the place of the name of (and, possibly, the host for) an affected user or a definer; in such cases, CURRENT_USER() [1287] is expanded where and as needed: • DROP USER • RENAME USER ...
Replication of DROP ... IF EXISTS Statements The DROP DATABASE IF EXISTS, DROP TABLE IF EXISTS, and DROP VIEW IF EXISTS statements are always replicated, even if the database, table, or view to be dropped does not exist on the master. This is to ensure that the object to be dropped no longer exis...
Replication Relay and Status Logs During replication, a slave server creates several logs that hold the binary log events relayed from the master to the slave, and to record information about the current status and location within the relay log. There are three types of logs used in the process, ...
Replication Solutions Replication can be used in many different environments for a range of purposes. This section provides general notes and advice on using replication for specific solution types. For information on using replication in a backup
Replication with Differing Table Definitions on Master and Slave Source and target tables for replication do not have to be identical. A table on the master can have more or fewer columns than the slave's copy of the table. In addition, corresponding table columns on the master and the slave can ...
Replication with Global Transaction Identifiers In this section, we discuss transaction-based replication using global transaction identifiers (GTIDs), introduced in MySQL 5.6.5. When using GTIDs, each transaction can be identified and tracked as it is committed on the originating server and appl...
Replication with More Columns on Master or Slave You can replicate a table from the master to the slave such that the master and slave copies of the table have differing numbers of columns, subject to the following conditions: • Columns common to both versions of the table must be defined in the ...
