Replication Features and Issues •If the source has databases with a character set different from the global  character_set_server value, you should design your  CREATE TABLE  statements so that they do not implicitly rely on the database default character set. A good workaround is to state the character set and collation explicitly in CREATE TABLE  statements. 17.5.1.4 Replication and CHECKSUM TABLE CHECKSUM TABLE  returns a checksum that is calculated row by row, using a method that depends on the table row storage format. The storage format is not guaranteed to remain the same between MySQL versions, so the checksum value might change following an upgrade. 17.5.1.5 Replication of CREATE SERVER, ALTER SERVER, and DROP SERVER The statements  CREATE SERVER ,  ALTER SERVER , and  DROP SERVER  are not written to the binary log, regardless of the binary logging format that is in use. 17.5.1.6 Replication of CREATE ... IF NOT EXISTS Statements MySQL applies these rules when various  CREATE ... IF NOT EXISTS  statements are replicated: •Every  CREATE DATABASE IF NOT EXISTS  statement is replicated, whether or not the database already exists on the source. •Similarly, every  CREATE TABLE IF NOT EXISTS  statement without a  SELECT  is replicated, whether or not the table already exists on the source. This includes  CREATE TABLE IF NOT EXISTS ... LIKE . Replication of  CREATE TABLE IF NOT EXISTS ... SELECT  follows somewhat different rules; see Section 17.5.1.7, “Replication of CREATE TABLE ... SELECT Statements” , for more information. • CREATE EVENT IF NOT EXISTS  is always replicated, whether or not the event named in the statement already exists on the source. 17.5.1.7 Replication of CREATE TABLE ... SELECT Statements MySQL applies these rules when  CREATE TABLE ... SELECT  statements are replicated: • CREATE TABLE ... SELECT  always performs an implicit commit (Section 13.3.3, “Statements That Cause an Implicit Commit” ). •If the destination table does not exist, logging occurs as follows. It does not matter whether  IF NOT EXISTS  is present. • STATEMENT  or  MIXED  format: The statement is logged as written. • ROW  format: The statement is logged as a  CREATE TABLE  statement followed by a series of insert-row events. Prior to MySQL 8.0.21, the statement is logged as two transactions. As of MySQL 8.0.21, on storage engines that support atomic DDL, it is logged as one transaction. For more information, see Section 13.1.1, “Atomic Data Definition Statement Support” . •If the  CREATE TABLE ... SELECT  statement fails, nothing is logged. This includes the case that the destination table exists and  IF NOT EXISTS  is not given. •If the destination table exists and  IF NOT EXISTS  is given, MySQL 8.0 ignores the statement completely; nothing is inserted or logged. MySQL 8.0 does not allow a  CREATE TABLE ... SELECT  statement to make any changes in tables other than the table that is created by the statement. 3656