Replication and Binary Logging Options and Variables regard to the logging format in effect, so the following statement-based rules for  --binlog-ignore-db always apply in determining whether or not the statement is logged. Statement-based logging.   Tells the server to not log any statement where the default database (that is, the one selected by  USE ) is  db_name . When there is no default database, no  --binlog-ignore-db  options are applied, and such statements are always logged. (Bug #11829838, Bug #60188) Row-based format.   Tells the server not to log updates to any tables in the database  db_name . The current database has no effect. When using statement-based logging, the following example does not work as you might expect. Suppose that the server is started with  --binlog-ignore-db=sales  and you issue the following statements: The  UPDATE  statement  is  logged in such a case because  --binlog-ignore-db  applies only to the default database (determined by the  USE  statement). Because the  sales  database was specified explicitly in the statement, the statement has not been filtered. However, when using row-based logging, the  UPDATE  statement’s effects are  not  written to the binary log, which means that no changes to the sales.january  table are logged; in this instance,  --binlog-ignore-db=sales  causes  all  changes made to tables in the source’s copy of the  sales  database to be ignored for purposes of binary logging. To specify more than one database to ignore, use this option multiple times, once for each database. Because database names can contain commas, the list is treated as the name of a single database if you supply a comma-separated list. You should not use this option if you are using cross-database updates and you do not want these updates to be logged. Checksum options.   MySQL supports reading and writing of binary log checksums. These are enabled using the two options listed here: Enabling this option causes the source to write checksums for events written to the binary log. Set to NONE  to disable, or the name of the algorithm to be used for generating checksums; currently, only CRC32 checksums are supported, and CRC32 is the default. You cannot change the setting for this option within a transaction. To control reading of checksums by the replica (from the relay log), use the  --slave-sql-verify- checksum  option. Testing and debugging options.   The following binary log options are used in replication testing and debugging. They are not intended for use in normal operations. 3545 • --binlog-checksum={NONE|CRC32} USE prices; UPDATE sales.january SET amount=amount+1000; Command-Line Format --binlog-checksum=type Type String Default Value CRC32 Valid Values NONE CRC32