Rechercher dans le manuel MySQL

17.4.1 Replication Features and Issues

[+/-]

17.4.1.1 Replication and AUTO_INCREMENT
17.4.1.2 Replication and BLACKHOLE Tables
17.4.1.3 Replication and Character Sets
17.4.1.4 Replication and CHECKSUM TABLE
17.4.1.5 Replication of CREATE SERVER, ALTER SERVER, and DROP SERVER
17.4.1.6 Replication of CREATE ... IF NOT EXISTS Statements
17.4.1.7 Replication of CREATE TABLE ... SELECT Statements
17.4.1.8 Replication of CURRENT_USER()
17.4.1.9 Replication with Differing Table Definitions on Master and Slave
17.4.1.10 Replication and DIRECTORY Table Options
17.4.1.11 Replication of DROP ... IF EXISTS Statements
17.4.1.12 Replication and Floating-Point Values
17.4.1.13 Replication and FLUSH
17.4.1.14 Replication and System Functions
17.4.1.15 Replication and Fractional Seconds Support
17.4.1.16 Replication of Invoked Features
17.4.1.17 Replication of JSON Documents
17.4.1.18 Replication and LIMIT
17.4.1.19 Replication and LOAD DATA
17.4.1.20 Replication and max_allowed_packet
17.4.1.21 Replication and MEMORY Tables
17.4.1.22 Replication of the mysql System Schema
17.4.1.23 Replication and the Query Optimizer
17.4.1.24 Replication and Partitioning
17.4.1.25 Replication and REPAIR TABLE
17.4.1.26 Replication and Reserved Words
17.4.1.27 Replication and Master or Slave Shutdowns
17.4.1.28 Slave Errors During Replication
17.4.1.29 Replication and Server SQL Mode
17.4.1.30 Replication and Temporary Tables
17.4.1.31 Replication Retries and Timeouts
17.4.1.32 Replication and Time Zones
17.4.1.33 Replication and Transaction Inconsistencies
17.4.1.34 Replication and Transactions
17.4.1.35 Replication and Triggers
17.4.1.36 Replication and TRUNCATE TABLE
17.4.1.37 Replication and User Name Length
17.4.1.38 Replication and Variables
17.4.1.39 Replication and Views

The following sections provide information about what is supported and what is not in MySQL replication, and about specific issues and situations that may occur when replicating certain statements.

Statement-based replication depends on compatibility at the SQL level between the master and slave. In other words, successful statement-based replication requires that any SQL features used be supported by both the master and the slave servers. If you use a feature on the master server that is available only in the current version of MySQL, you cannot replicate to a slave that uses an earlier version of MySQL. Such incompatibilities can also occur within a release series as well as between versions.

If you are planning to use statement-based replication between MySQL 8.0 and a previous MySQL release series, it is a good idea to consult the edition of the MySQL Reference Manual corresponding to the earlier release series for information regarding the replication characteristics of that series.

With MySQL's statement-based replication, there may be issues with replicating stored routines or triggers. You can avoid these issues by using MySQL's row-based replication instead. For a detailed list of issues, see Section 24.7, “Stored Program Binary Logging”. For more information about row-based logging and row-based replication, see Section 5.4.4.1, “Binary Logging Formats”, and Section 17.2.1, “Replication Formats”.

For additional information specific to replication and InnoDB, see Section 15.18, “InnoDB and MySQL Replication”. For information relating to replication with NDB Cluster, see Section 22.6, “NDB Cluster Replication”.


Find a PHP function

Document created the 26/06/2006, last modified the 26/10/2018
Source of the printed document:https://www.gaudry.be/en/mysql-rf-replication-features.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:en Manuel MySQL : https://dev.mysql.com/

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut