MySQL 8.4 Release Notes
19.5.1 复制 Features and Issues
- 19.5.1.1 复制 and AUTO_INCREMENT
- 19.5.1.2 复制 and BLACKHOLE Tables
- 19.5.1.3 复制 and Character Sets
- 19.5.1.4 复制 and CHECKSUM TABLE
- 19.5.1.5 复制 of CREATE SERVER, ALTER SERVER, and DROP SERVER
- 19.5.1.6 复制 of CREATE ... IF NOT EXISTS Statements
- 19.5.1.7 Replication of 创建表...选择语句s
- 19.5.1.8 复制 of CURRENT_USER()
- 19.5.1.9 复制 with Differing Table Definitions on Source and Replica
- 19.5.1.10 复制 and DIRECTORY Table Options
- 19.5.1.11 复制 of DROP ... IF EXISTS Statements
- 19.5.1.12 复制 and Floating-Point Values
- 19.5.1.13 复制 and FLUSH
- 19.5.1.14 复制 and System Functions
- 19.5.1.15 复制 and Fractional Seconds Support
- 19.5.1.16 复制 of Invoked Features
- 19.5.1.17 复制 of JSON Documents
- 19.5.1.18 复制 and LIMIT
- 19.5.1.19 复制 and LOAD DATA
- 19.5.1.20 复制 and max_allowed_packet
- 19.5.1.21 复制 and MEMORY Tables
- 19.5.1.22 复制 of the mysql System Schema
- 19.5.1.23 复制 and the Query Optimizer
- 19.5.1.24 复制 and Partitioning
- 19.5.1.25 复制 and REPAIR TABLE
- 19.5.1.26 复制 and Reserved Words
- 19.5.1.27 复制 and Row Searches
- 19.5.1.28 复制 and Source or Replica Shutdowns
- 19.5.1.29 Replica Errors During 复制
- 19.5.1.30 复制 and Server SQL Mode
- 19.5.1.31 复制 and Temporary Tables
- 19.5.1.32 复制 Retries and Timeouts
- 19.5.1.33 复制 and Time Zones
- 19.5.1.34 复制 and Transaction Inconsistencies
- 19.5.1.35 复制 and Transactions
- 19.5.1.36 复制 and Triggers
- 19.5.1.37 复制 and TRUNCATE TABLE
- 19.5.1.38 复制 and User Name Length
- 19.5.1.39 复制 and Variables
- 19.5.1.40 复制 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 source and replica. In other words, successful statement-based replication requires that any SQL features used be supported by both the source and the replica servers. If you use a feature on the source server that is available only in the current version of MySQL, you cannot replicate to a replica 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.4 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 27.7, “Stored Program Binary Logging”. For more information about row-based logging and row-based replication, see Section 7.4.4.1, “Binary Logging Formats”, and Section 19.2.1, “Replication Formats”.
For additional information specific to replication and InnoDB, see Section 17.19, “InnoDB and MySQL Replication”. For information relating to replication with NDB Cluster, see Section 25.7, “NDB Cluster Replication”.