Skip navigation links
5.2.4.4 Logging Format for Changes to mysql Database Tables »
Section Navigation      [Toggle]

5.2.4.3. Mixed Binary Logging Format

When running in MIXED mode, automatic switching from statement-based to row-based replication takes place under the following conditions:

Note

Starting with MySQL 5.1.20 a warning is generated if you try to log execute a statement in statement-logging mode that should be logged in row-logging mode. The warning is shown both in the client (in the output of SHOW WARNINGS) and through the mysqld error log. A warning is added to the SHOW WARNINGS table each time a statement is executed. However, only the first statement that generated the warning for each client session is logged to the mysqld error log to prevent flooding the error log.

Starting with MySQL 5.1.20, in addition to the decisions above, individual engines can also determine the logging format used when information in a table is updated. The following table lists the logging formats supported by each storage engine:

Storage Engine Row Logging Supported Statement Logging Supported
ARCHIVE Yes Yes
BLACKHOLE Yes Yes
CSV Yes Yes
EXAMPLE Yes No
FEDERATED Yes Yes
HEAP Yes Yes
InnoDB Yes Yes, when the transaction isolation level is REPEATABLE READ or SERIALIZABLE; otherwise, No.
MyISAM Yes Yes
MERGE Yes Yes
NDBCLUSTER Yes No

A given storage engine can support either or both logging formats; the logging capabilities of an individual engine can be further defined as follows:

  • If an engine supports row-based logging, the engine is said to be row-logging capable.

  • If an engine supports statement-based logging, the engine is said to be statement-logging capable.

When determining the logging mode to be used, the capabilities of all the tables affected by the event are combined. The set of affected tables is then marked according to these rules:

  • A set of tables is defined as row logging restricted if the tables are row logging capable but not statement logging capable.

  • A set of tables is defined as statement logging restricted if the tables are statement logging capable but not row logging capable.

Once the determination of the possible logging formats required by the statement is complete it is compared to the current binlog_format setting. The following table is used to decide how the information is recorded in the binary log or, if appropriate, whether an error is raised. In the table, a safe operation is defined as one that is deterministic. A number of rules decide whether the statement is deterministic or not, as shown in the following table (where RLR stands for “row-logging restricted” and SLR stands for “statement-logging restricted”).

Condition Action
Safe/unsafe binlog_format RLR SLR Error/Warning Logged as
Safe STATEMENT Y Y Error: not loggable  
Safe STATEMENT Y N   STATEMENT
Safe STATEMENT N Y Error: not loggable  
Safe STATEMENT N N   STATEMENT
Safe MIXED Y Y Error: not loggable  
Safe MIXED Y N   STATEMENT
Safe MIXED N Y   ROW
Safe MIXED N N   STATEMENT
Safe ROW Y Y Error: not loggable  
Safe ROW Y N Error: not loggable  
Safe ROW N Y   ROW
Safe ROW N N   ROW
Unsafe STATEMENT Y Y Error: not loggable  
Unsafe STATEMENT Y N Warning: unsafe STATEMENT
Unsafe STATEMENT N Y Error: not loggable  
Unsafe STATEMENT N N Warning: unsafe STATEMENT
Unsafe MIXED Y Y Error: not loggable  
Unsafe MIXED Y N Error: not loggable  
Unsafe MIXED N Y   ROW
Unsafe MIXED N N   ROW
Unsafe ROW Y Y Error: not loggable  
Unsafe ROW Y N Error: not loggable  
Unsafe ROW N Y   ROW
Unsafe ROW N N   ROW

When a warning is produced by the determination, a standard MySQL warning is produced (and is available using SHOW WARNINGS). The information is also written to the mysqld error log. Only one error for each error instance per client connection is logged. The log message will include the SQL statement that was attempted.

If a slave server was started with --log-warnings enabled, the slave prints messages to the error log to provide information about its status, such as the binary log and relay log coordinates where it starts its job, when it is switching to another relay log, when it reconnects after a disconnect, and so forth.