MySQL 8.4 Release Notes
- 19.5.1.1 复制与 AUTO_INCREMENT19.5.1.1 Replication and AUTO_INCREMENT
- 19.5.1.2 复制与 BLACKHOLE 表19.5.1.2 Replication and BLACKHOLE Tables
- 19.5.1.3 复制与字符集19.5.1.3 Replication and Character Sets
- 19.5.1.4 复制与 CHECKSUM TABLE19.5.1.4 Replication and CHECKSUM TABLE
- 19.5.1.5 CREATE SERVER、ALTER SERVER 和 DROP SERVER 的复制19.5.1.5 Replication of CREATE SERVER, ALTER SERVER, and DROP SERVER
- 19.5.1.6 CREATE ... IF NOT EXISTS 语句的复制19.5.1.6 Replication of CREATE ... IF NOT EXISTS Statements
- 19.5.1.7 CREATE TABLE ... SELECT 语句的复制19.5.1.7 Replication of CREATE TABLE ... SELECT Statements
- 19.5.1.8 CURRENT_USER() 的复制19.5.1.8 Replication of CURRENT_USER()
- 19.5.1.9 源和副本表定义不同的复制19.5.1.9 Replication with Differing Table Definitions on Source and Replica
- 19.5.1.10 复制与 DIRECTORY 表选项19.5.1.10 Replication and DIRECTORY Table Options
- 19.5.1.11 DROP ... IF EXISTS 语句的复制19.5.1.11 Replication of DROP ... IF EXISTS Statements
- 19.5.1.12 复制和浮点值19.5.1.12 Replication and Floating-Point Values
- 19.5.1.13 复制和 FLUSH19.5.1.13 Replication and FLUSH
- 19.5.1.14 复制和系统函数19.5.1.14 Replication and System Functions
- 19.5.1.15 复制和分数秒支持19.5.1.15 Replication and Fractional Seconds Support
- 19.5.1.16 调用功能的复制19.5.1.16 Replication of Invoked Features
- 19.5.1.17 JSON 文档的复制19.5.1.17 Replication of JSON Documents
- 19.5.1.18 复制和 LIMIT19.5.1.18 Replication and LIMIT
- 19.5.1.19 复制与 LOAD DATA19.5.1.19 Replication and LOAD DATA
- 19.5.1.20 复制与 max_allowed_packet19.5.1.20 Replication and max_allowed_packet
- 19.5.1.21 复制与 MEMORY 表19.5.1.21 Replication and MEMORY Tables
- 19.5.1.22 mysql 系统架构的复制19.5.1.22 Replication of the mysql System Schema
- 19.5.1.23 复制与查询优化器19.5.1.23 Replication and the Query Optimizer
- 19.5.1.24 复制与分区19.5.1.24 Replication and Partitioning
- 19.5.1.25 复制与 REPAIR TABLE19.5.1.25 Replication and REPAIR TABLE
- 19.5.1.26 复制与保留字19.5.1.26 Replication and Reserved Words
- 19.5.1.27 复制与行搜索19.5.1.27 Replication and Row Searches
- 19.5.1.28 复制与源或副本关闭19.5.1.28 Replication and Source or Replica Shutdowns
- 19.5.1.29 复制期间副本错误19.5.1.29 Replica Errors During Replication
- 19.5.1.30 复制与服务器 SQL 模式19.5.1.30 Replication and Server SQL Mode
- 19.5.1.31 复制与临时表19.5.1.31 Replication and Temporary Tables
- 19.5.1.32 复制重试与超时19.5.1.32 Replication Retries and Timeouts
- 19.5.1.33 复制与时区19.5.1.33 Replication and Time Zones
- 19.5.1.34 复制与事务不一致性19.5.1.34 Replication and Transaction Inconsistencies
- 19.5.1.35 复制与事务19.5.1.35 Replication and Transactions
- 19.5.1.36 复制与触发器19.5.1.36 Replication and Triggers
- 19.5.1.37 复制与 TRUNCATE TABLE19.5.1.37 Replication and TRUNCATE TABLE
- 19.5.1.38 复制与用户名长度19.5.1.38 Replication and User Name Length
- 19.5.1.39 复制与变量19.5.1.39 Replication and Variables
- 19.5.1.40 复制与视图19.5.1.40 Replication and Views
以下各节提供了有关 MySQL 复制中支持和不支持内容的信息，以及在复制某些语句时可能出现的特定问题和情况。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.
基于语句的复制依赖于源和副本在 SQL 级别的兼容性。换句话说，成功的基于语句的复制要求使用的任何 SQL 功能都必须被源服务器和副本服务器支持。如果您在源服务器上使用某个仅在当前版本的 MySQL 中可用的功能，则无法复制到使用旧版本 MySQL 的副本中。这种不兼容性也可能在同一发布系列内部以及不同版本之间发生。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.
如果您计划在 MySQL 8.4 与早期 MySQL 发行系列之间使用基于语句的复制，建议查阅对应早期发行系列的 MySQL 参考手册 版本，以获取有关该系列复制特性的信息。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.
在 MySQL 的基于语句的复制中，复制存储例程或触发器时可能会出现问题。您可以通过使用 MySQL 的基于行的复制来避免这些问题。有关问题的详细列表，请参见 第 27.7 节，“存储程序二进制日志记录”。有关基于行的日志记录和基于行的复制的更多信息，请参见 第 7.4.4.1 节，“二进制日志记录格式”，以及 第 19.2.1 节，“复制格式”。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”.
有关特定于复制和InnoDB的其他信息，请参见第 17.19 节，“InnoDB 和 MySQL 复制”。有关使用 NDB 集群进行复制的信息，请参见第 25.7 节，“NDB 集群复制”。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”.