1. 环境描述
目的：当数据库中设置了binlog-do-db时，在不同的binlog_format=statement | row | mixed 下对binlog的写入影响，这个在主从复制中会有一些坑，由于binlog的写入不完全，极有可能会导致主从不一致的情况的。
blog地址：http://blog.csdn.net/hw_libo/article/details/40476577
SuSE 11 sp1 x86_64 + MySQL 5.5.37
参数设置：
binlog-do-db = bosco1
测试样例1：
use bosco2; create table bosco1.bosco1_tb01(id int); create table bosco2.bosco2_tb01(id int); insert into bosco1.bosco1_tb01(id) values(1); insert into bosco2.bosco2_tb01(id) values(1);测试样例2：
use bosco1; create table bosco1.bosco1_tb01(id int); create table bosco2.bosco2_tb01(id int); insert into bosco1.bosco1_tb01(id) values(1); insert into bosco2.bosco2_tb01(id) values(1);
2. 测试1：use bosco2及SBR/RBR/MBR下
binlog-do-db=bosco1; MySQL [(none)]> use bosco2; Database changed MySQL [bosco2]> select @@tx_isolation,@@binlog_format; +-----------------+-----------------+ | @@tx_isolation | @@binlog_format | +-----------------+-----------------+ | REPEATABLE-READ | STATEMENT | +-----------------+-----------------+ 1 row in set (0.00 sec) MySQL [bosco1]> flush logs; Query OK, 0 rows affected (0.00 sec) MySQL [bosco1]> create table bosco1.bosco1_tb01(id int); Query OK, 0 rows affected (0.01 sec) MySQL [bosco1]> create table bosco2.bosco2_tb01(id int); Query OK, 0 rows affected (0.00 sec) MySQL [bosco1]> insert into bosco1.bosco1_tb01(id) values(1); Query OK, 1 row affected (0.01 sec) MySQL [bosco1]> insert into bosco2.bosco2_tb01(id) values(1); Query OK, 1 row affected (0.00 sec) MySQL [bosco1]> flush logs; Query OK, 0 rows affected (0.01 sec)
那么来查看一下上面的操作有没有写入binlog中：
# mysqlbinlog --verbose --base64-output=decode-rows mysql-bin.000013 /*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/; /*!40019 SET @@session.max_insert_delayed_threads=0*/; /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/; DELIMITER /*!*/; # at 4 #141026 1:41:09 server id 1303308 end_log_pos 107 Start: binlog v 4, server v 5.5.37-log created 141026 1:41:09 # at 107 #141026 1:43:02 server id 1303308 end_log_pos 150 Rotate to mysql-bin.000014 pos: 4 DELIMITER ; # End of log file ROLLBACK /* added by mysqlbinlog */; /*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/; /*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=0*/;可见，指定了binlog-do-db=bosco1，事务隔离级别RR + binlog_format=statement或是row，在使用其他database（非bosco1数据库）下的所有操作都不会记录到binlogs中，即使是操作binlog-do-db=bosco1下的表；而且DDL也不会被记录。
3. 测试2：use bosco1及RBR下
binlog-do-db=bosco1; MySQL [bosco2]> use bosco1; MySQL [bosco1]> select @@tx_isolation,@@binlog_format; +-----------------+-----------------+ | @@tx_isolation | @@binlog_format | +-----------------+-----------------+ | REPEATABLE-READ | ROW | +-----------------+-----------------+ 1 row in set (0.00 sec) MySQL [bosco1]> flush logs; Query OK, 0 rows affected (0.00 sec) MySQL [bosco1]> create table bosco1.bosco1_tb01(id int); Query OK, 0 rows affected (0.01 sec) MySQL [bosco1]> create table bosco2.bosco2_tb01(id int); Query OK, 0 rows affected (0.00 sec) MySQL [bosco1]> insert into bosco1.bosco1_tb01(id) values(1); Query OK, 1 row affected (0.01 sec) MySQL [bosco1]> insert into bosco2.bosco2_tb01(id) values(1); Query OK, 1 row affected (0.00 sec) MySQL [bosco1]> flush logs; Query OK, 0