220.127.116.11 Replication of CREATE TABLE ... SELECT Statements
This section discusses how MySQL replicates
CREATE TABLE ... SELECT statements.
MySQL 5.7 does not allow a
CREATE TABLE ... SELECT statement to make any changes in tables other than the table that is created by the statement. Some older versions of MySQL permitted these statements to do so; this means that, when using statement-based replication between a MySQL 5.6 or later replica and a source running a previous version of MySQL, a
CREATE TABLE ... SELECT statement causing changes in other tables on the source fails on the replica, causing replication to stop. To prevent this from happening, you should use row-based replication, rewrite the offending statement before running it on the source, or upgrade the source to MySQL 5.7. (If you choose to upgrade the source, keep in mind that such a
CREATE TABLE ... SELECT statement fails following the upgrade unless it is rewritten to remove any side effects on other tables.) This is not an issue when using row-based replication, because the statement is logged as a
CREATE TABLE statement with any changes to table data logged as row-insert events, rather than as the entire
CREATE TABLE ... SELECT.
These behaviors are not dependent on MySQL version:
CREATE TABLE ... SELECTalways performs an implicit commit (Section 13.3.3, “Statements That Cause an Implicit Commit”).
If destination table does not exist, logging occurs as follows. It does not matter whether
IF NOT EXISTSis present.
MIXEDformat: The statement is logged as written.
ROWformat: The statement is logged as a
CREATE TABLEstatement followed by a series of insert-row events.
If the statement fails, nothing is logged. This includes the case that the destination table exists and
IF NOT EXISTSis not given.
When the destination table exists and
IF NOT EXISTS is given, MySQL 5.7 ignores the statement completely; nothing is inserted or logged.