load data语句如何保证主备复制数据一致性(一)

  • 背景

    • 机器配置
      * CPU:16 vcpus
      * 磁盘:100G flash卡 data&binlog混用
      * 内存:64G
    • 数据库版本:MySQL 5.7.18
    • 数据库IP信息:主库IP 10.10.30.241,从库IP 10.10.30.250

    • 数据库参数配置:
      * 主库:双一,log_slave_updates,log-bin,secure_file_priv='',server-id=3306241,binlog_rows_query_log_events=ON,sql_mode='ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'
      * 从库:双一,log_slave_updates,log-bin,binlog_rows_query_log_events=ON,server-id=3306250,sql_mode='ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'

    • 测试目的:通过示例演示并查看过程中binlog中如何记录load data语句等方式来验证 load data语句如何保证主备复制数据一致性
      * 将分别在四种隔离级别下(会话级别修改tx_isolation)针对binlog_format(会话级别修改binlog_format)的三种格式分别进行演示执行load data语句,观察MySQL server层如何处理,主库binlog中如何记录load data语句,备库的binlog中如何如何记录load data语句
      * 本文假定你已经搭建好了主备复制环境,如果未搭建请先自行搭建主备复制环境

    • PS:本文仅针对测试目的做验证演示,关于binlog_format三种格式以及事务的四种隔离级别详细说明请查阅相关资料,本文不做解读
      * binlog_format参考资料:https://dev.mysql.com/doc/refman/5.7/en/replication-formats.html
      * 事务隔离级别参考资料:https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html

1、制造测试数据

  • 建库
 
 
    1. admin@localhost : (none) 07:34:39> create database if not exists xiaoboluo;
    2. Query OK, 1 row affected (0.00 sec)
  • 建表
 
 
    1. admin@localhost : (none) 10:04:52> use xiaoboluo
    2. Database changed
    3. admin@localhost : xiaoboluo 10:04:57> create table if not exists test_load(id int unsigned not null primary key auto_increment,test varchar(100));
    4. Query OK, 0 rows affected (0.01 sec)
  • 插入测试数据
 
 
    1. admin@localhost : xiaoboluo 10:05:32> insert into test_load(test) values('1'),('2'),('null'),('4');
    2. Query OK, 4 rows affected (0.01 sec)
    3. Records: 4 Duplicates: 0 Warnings: 0
    4.  
    5.  
    6. admin@localhost : xiaoboluo 10:06:01> select * from test_load;
    7. +----+------+
    8. | id | test |
    9. +----+------+
    10. | 2 | 1 |
    11. | 4 | 2 |
    12. | 6 | null |
    13. | 8 | 4 |
    14. +----+------+
    15. 4 rows in set (0.00 sec)
  • 执行select …into outifile语句生成load data需要的数据文本文件
 
 
    1. admin@localhost : xiaoboluo 10:12:41> select * from test_load into outfile "/tmp/test_load.txt";
    2. Query OK, 4 rows affected (0.01 sec)
    3.  
    4.  
    5. admin@localhost : xiaoboluo 10:12:42> system cat /tmp/test_load.txt;
    6. 2 1
    7. 4 2
    8. 6 null
    9. 8 4

2、read-uncommitted隔离级别

2.1. binlog_format=statement
  • 先在主库中把binlog_format修改为statement,隔离级别修改为read-uncommitted,并刷新主从库binlog
 
 
    1. # 主库
    2. admin@localhost : xiaoboluo 09:37:09> set binlog_format=statement;
    3. Query OK, 0 rows affected (0.00 sec)
    4.  
    5.  
    6. admin@localhost : xiaoboluo 09:39:24> set tx_isolation='read-uncommitted';
    7. Query OK, 0 rows affected (0.00 sec)
    8.  
    9.  
    10. admin@localhost : xiaoboluo 09:39:44> flush binary logs;
    11. Query OK, 0 rows affected (0.01 sec)
    12.  
    13.  
    14. # 从库
    15. mysql> flush binary logs;
    16. Query OK, 0 rows affected (0.01 sec)
    17.  
    18.  
    19. mysql>
  • 主库清空表test_load并执行load data语句
 
 
    1. admin@localhost : xiaoboluo 09:39:54> truncate test_load;
    2. Query OK, 0 rows affected (0.00 sec)
    3. admin@localhost : xiaoboluo 09:41:13> load data infile '/tmp/test_load.txt' into table test_load;
    4. ERROR 1665 (HY000): Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.
    5. Error (Code 1665): Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.
    6. Error (Code 1015): Can
  • 从以上结果中可以看到,在RU隔离级别下,binlog_format设置为statement不允许load data语句执行,从报错信息上可以看到,在RC和RU隔离级别下,binlog只能以row格式记录,所以statement无法记录binlog
  • 查看主库表test_load中的数据
 
 
    1. admin@localhost : xiaoboluo 09:41:52> select * from test_load;
    2. Empty set (0.00 sec)
  • 从以上结果中可以看到,表数据并没有导入成功,现在解析binlog查看一下
 
 
    1. [root@5f1772e3-0c7a-4537-97f9-9b57cf6a04c2 binlog]# ll
    2. total 196
    3. -rw-r----- 1 mysql mysql 4916 May 4 00:11 mysql-bin.000014
    4.  
    5. -rw-r----- 1 mysql mysql 4557 May 4 00:12 mysql-bin.000015
    6. -rw-r----- 1 mysql mysql 5595 May 4 09:39 mysql-bin.000016
    7. -rw-r----- 1 mysql mysql 366 May 4 09:41 mysql-bin.000017
    8. -rw-r----- 1 mysql mysql 884 May 4 09:39 mysql-bin.index
    9. [root@5f1772e3-0c7a-4537-97f9-9b57cf6a04c2 binlog]# mysqlbinlog -vvv --base64-output=decode-rows mysql-bin.000017
    10. ......
    11. use `xiaoboluo`/*!*/;
    12. ......
    13. truncate test_load
    14. /*!*/;
    15. SET @@SESSION.GTID_NEXT= 'AUTOMATIC' /* added by mysqlbinlog */ /*!*/;
    16. DELIMITER ;
    17. # End of log file
    18. ......
  • 从上面的结果中可以看到,解析binlog的结果中除了use db和truncate table语句之外,没有其他的操作了,说明并没有数据写入,load data语句被mysql server直接拒绝执行了
2.2. binlog_format=mixed
  • 先在主库中把binlog_format修改为mixed,隔离级别不要动,并刷新主从库binlog
 
 
    1. # 主库
    2. admin@localhost : xiaoboluo 09:44:05> set binlog_format=mixed;
    3. Query OK, 0 rows affected (0.00 sec)
    4.  
    5.  
    6. admin@localhost : xiaoboluo 09:49:49> flush binary logs;
    7. Query OK, 0 rows affected (0.01 sec)
    8.  
    9.  
    10. # 从库
    11. mysql> flush binary logs;
    12. Query OK, 0 rows affected (0.01 sec)
    13.  
    14.  
    15. mysql>
  • 主库清空表test_load并执行load data语句
 
 
    1. admin@localhost : xiaoboluo 09:49:57> truncate test_load;
    2. Query OK, 0 rows affected (0.01 sec)
    3.  
    4.  
    5. admin@localhost : xiaoboluo 09:51:12> load data infile '/tmp/test_load.txt' into table test_load;
    6. Query OK, 4 rows affected (0.00 sec)
    7. Records: 4 Deleted: 0 Skipped: 0 Warnings: 0
  • 从以上结果中可以看到,在RU隔离级别下,binlog_format设置为mixed允许load data语句执行
  • 查看主库表test_load中的数据
 
 
    1. admin@localhost : xiaoboluo 09:51:24> select * from test_load;
    2. +----+------+
    3. | id | test |
    4. +----+------+
    5. | 2 | 1 |
    6. | 4 | 2 |
    7. | 6 | null |
    8. | 8 | 4 |
    9. +----+------+
    10. 4 rows in set (0.00 sec)
  • 从以上结果中可以看到,表数据导入成功,现在解析binlog查看一下
 
 
    1. [root@5f1772e3-0c7a-4537-97f9-9b57cf6a04c2 binlog]# ll
    2. total 196
    3. -rw-r----- 1 mysql mysql 4916 May 4 00:11 mysql-bin.000014
    4. -rw-r----- 1 mysql mysql 4557 May 4 00:12 mysql-bin.000015
    5. -rw-r----- 1 mysql mysql 5595 May 4 09:39 mysql-bin.000016
    6. -rw-r----- 1 mysql mysql 366 May 4 09:41 mysql-bin.000017
    7. -rw-r----- 1 mysql mysql 744 May 4 09:51 mysql-bin.000018
    8. -rw-r----- 1 mysql mysql 936 May 4 09:49 mysql-bin.index
    9. [root@5f1772e3-0c7a-4537-97f9-9b57cf6a04c2 binlog]# mysqlbinlog -vv --base64-output=decode-rows mysql-bin.000018
    10. # at 259
    11. #170504 9:51:12 server id 3306241 end_log_pos 354 CRC32 0xff83f0ce Query thread_id=155 exec_time=0 error_code=0
    12. use `xiaoboluo`/*!*/;
    13. ......
    14. truncate test_load
    15. ......
    16. BEGIN
    17. /*!*/;
    18. # at 501
    19. #170504 9:51:24 server id 3306241 end_log_pos 583 CRC32 0xfef1767a Rows_query
    20. # load data infile '/tmp/test_load.txt' into table test_load # 这里可以看到load data语句在这里,这里是开启了参数binlog_rows_query_log_events=ON之后记录的原生sql,默认被加了注释,主备复制不会执行
    21. # at 583
    22. #170504 9:51:24 server id 3306241 end_log_pos 643 CRC32 0x349b62a4 Table_map: `xiaoboluo`.`test_load` mapped to number 340
    23. # at 643
    24. #170504 9:51:24 server id 3306241 end_log_pos 713 CRC32 0x4ceacc10 Write_rows: table id 340 flags: STMT_END_F
    25. ### INSERT INTO `xiaoboluo`.`test_load` #这里是用于主备复制的数据变更日志,可以看到在mixed格式下被转换为了row格式
    26. ### SET
    27. ### @1=2 /* INT meta=0 nullable=0 is_null=0 */
    28. ### @2='1' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    29. ### INSERT INTO `xiaoboluo`.`test_load`
    30. ### SET
    31. ### @1=4 /* INT meta=0 nullable=0 is_null=0 */
    32. ### @2='2' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    33. ### INSERT INTO `xiaoboluo`.`test_load`
    34. ### SET
    35. ### @1=6 /* INT meta=0 nullable=0 is_null=0 */
    36. ### @2='null' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    37. ### INSERT INTO `xiaoboluo`.`test_load`
    38. ### SET
    39. ### @1=8 /* INT meta=0 nullable=0 is_null=0 */
    40. ### @2='4' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    41. # at 713
    42. #170504 9:51:24 server id 3306241 end_log_pos 744 CRC32 0xfa76965b Xid = 1237
    43. COMMIT/*!*/;
    44. SET @@SESSION.GTID_NEXT= 'AUTOMATIC' /* added by mysqlbinlog */ /*!*/;
    45. DELIMITER ;
    46. # End of log file
    47. /*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
    48. /*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=0*/
  • 从上面解析binlog的结果中可以看到,数据写入成功,load data语句被转换为row格式记录在binlog中

  • 查看备库中数据是否正确复制

 
 
    1. mysql> use xiaoboluo
    2. Reading table information for completion of table and column names
    3. You can turn off this feature to get a quicker startup with -A
    4.  
    5.  
    6. Database changed
    7. mysql> select * from test_load;
    8. +----+------+
    9. | id | test |
    10. +----+------+
    11. | 2 | 1 |
    12. | 4 | 2 |
    13. | 6 | null |
    14. | 8 | 4 |
    15. +----+------+
    16. 4 rows in set (0.00 sec)
  • 解析备库binlog中是如何记录的load data语句
 
 
    1. [root@e710d318-d5b4-4bc7-a606-d09f06ff5f5d binlog]# ll
    2. total 100
    3. -rw-r----- 1 mysql mysql 990 May 1 01:36 mysql-bin.000001
    4. -rw-r----- 1 mysql mysql 54766 May 4 00:02 mysql-bin.000002
    5. -rw-r----- 1 mysql mysql 21376 May 4 09:40 mysql-bin.000003
    6. -rw-r----- 1 mysql mysql 401 May 4 09:50 mysql-bin.000004
    7. -rw-r----- 1 mysql mysql 730 May 4 09:51 mysql-bin.000005
    8. -rw-r----- 1 mysql mysql 260 May 4 09:50 mysql-bin.index
    9. [root@e710d318-d5b4-4bc7-a606-d09f06ff5f5d binlog]# mysqlbinlog -vv --base64-output=decode-rows mysql-bin.000005
    10. ...
    11. #170504 9:51:12 server id 3306241 end_log_pos 354 CRC32 0xff83f0ce Query thread_id=155 exec_time=0 error_code=0
    12. use `xiaoboluo`/*!*/;
    13. ...
    14. truncate test_load
    15. ...
    16. BEGIN
    17. /*!*/;
    18. # at 487
    19. #170504 9:51:24 server id 3306241 end_log_pos 569 CRC32 0x67a31998 Rows_query
    20. # load data infile '/tmp/test_load.txt' into table test_load # 这里可以看到load data语句在这里,这里是开启了参数binlog_rows_query_log_events=ON之后记录的原生sql,默认被加了注释,主备复制不会执行
    21. # at 569
    22. #170504 9:51:24 server id 3306241 end_log_pos 629 CRC32 0x6420d19b Table_map: `xiaoboluo`.`test_load` mapped to number 301
    23. # at 629
    24. #170504 9:51:24 server id 3306241 end_log_pos 699 CRC32 0xf5fff0d8 Write_rows: table id 301 flags: STMT_END_F
    25. ### INSERT INTO `xiaoboluo`.`test_load` #这里是备库记录的主库binlog日志,可以看到在mixed格式下被转换为了row格式
    26. ### SET
    27. ### @1=2 /* INT meta=0 nullable=0 is_null=0 */
    28. ### @2='1' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    29. ### INSERT INTO `xiaoboluo`.`test_load`
    30. ### SET
    31. ### @1=4 /* INT meta=0 nullable=0 is_null=0 */
    32. ### @2='2' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    33. ### INSERT INTO `xiaoboluo`.`test_load`
    34. ### SET
    35. ### @1=6 /* INT meta=0 nullable=0 is_null=0 */
    36. ### @2='null' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    37. ### INSERT INTO `xiaoboluo`.`test_load`
    38. ### SET
    39. ### @1=8 /* INT meta=0 nullable=0 is_null=0 */
    40. ### @2='4' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    41. # at 699
    42. #170504 9:51:24 server id 3306241 end_log_pos 730 CRC32 0xd5a3bda4 Xid = 424
    43. COMMIT/*!*/;
    44. ...
2.3. binlog_format=row
  • 先在主库中把binlog_format修改为row,隔离级别不要动,并刷新主从库binlog
 
 
    1. # 主库
    2. admin@localhost : xiaoboluo 11:05:20> set binlog_format=row;
    3. Query OK, 0 rows affected (0.00 sec)
    4. admin@localhost : xiaoboluo 11:18:23> flush binary logs;
    5. Query OK, 0 rows affected (0.01 sec)
    6. # 从库
    7. mysql> flush binary logs;
    8. Query OK, 0 rows affected (0.01 sec)
    9. mysql>
  • 主库清空表test_load并执行load data语句
 
 
    1. admin@localhost : xiaoboluo 11:18:26> truncate test_load;
    2. Query OK, 0 rows affected (0.01 sec)
    3. admin@localhost : xiaoboluo 11:18:51> load data infile '/tmp/test_load.txt' into table test_load;
    4. Query OK, 4 rows affected (0.00 sec)
    5. Records: 4 Deleted: 0 Skipped: 0 Warnings: 0
  • 从以上结果中可以看到,在RU隔离级别下,binlog_format设置为row允许load data语句执行
  • 查看主库表test_load中的数据
 
 
    1. admin@localhost : xiaoboluo 11:18:57> select * from test_load;
    2. +----+------+
    3. | id | test |
    4. +----+------+
    5. | 2 | 1 |
    6. | 4 | 2 |
    7. | 6 | null |
    8. | 8 | 4 |
    9. +----+------+
    10. 4 rows in set (0.00 sec)
  • 从以上结果中可以看到,表数据导入成功,现在解析binlog查看一下
 
 
    1. [root@5f1772e3-0c7a-4537-97f9-9b57cf6a04c2 binlog]# ll
    2. total 196
    3. -rw-r----- 1 mysql mysql 4916 May 4 00:11 mysql-bin.000014
    4. -rw-r----- 1 mysql mysql 4557 May 4 00:12 mysql-bin.000015
    5. -rw-r----- 1 mysql mysql 5595 May 4 09:39 mysql-bin.000016
    6. -rw-r----- 1 mysql mysql 366 May 4 09:41 mysql-bin.000017
    7. -rw-r----- 1 mysql mysql 744 May 4 09:51 mysql-bin.000018
    8. -rw-r----- 1 mysql mysql 744 May 4 11:18 mysql-bin.000019
    9. -rw-r----- 1 mysql mysql 988 May 4 11:18 mysql-bin.index
    10. [root@5f1772e3-0c7a-4537-97f9-9b57cf6a04c2 binlog]# mysqlbinlog -vv --base64-output=decode-rows mysql-bin.000018
    11. # at 259
    12. #170504 11:18:51 server id 3306241 end_log_pos 354 CRC32 0x9d5985ad Query thread_id=155 exec_time=0 error_code=0
    13. use `xiaoboluo`/*!*/;
    14. ......
    15. truncate test_load
    16. ......
    17. BEGIN
    18. /*!*/;
    19. # at 501
    20. #170504 11:18:57 server id 3306241 end_log_pos 583 CRC32 0x0e8f7603 Rows_query
    21. # load data infile '/tmp/test_load.txt' into table test_load # 这里可以看到load data语句在这里,这里是开启了参数binlog_rows_query_log_events=ON之后记录的原生sql,默认被加了注释,主备复制不会执行
    22. # at 583
    23. #170504 11:18:57 server id 3306241 end_log_pos 643 CRC32 0xe1c5d4d0 Table_map: `xiaoboluo`.`test_load` mapped to number 341
    24. # at 643
    25. #170504 11:18:57 server id 3306241 end_log_pos 713 CRC32 0x31619df3 Write_rows: table id 341 flags: STMT_END_F
    26. ### INSERT INTO `xiaoboluo`.`test_load` #这里是用于主备复制的数据变更日志,可以看到在row格式下被转换为了row格式
    27. ### SET
    28. ### @1=2 /* INT meta=0 nullable=0 is_null=0 */
    29. ### @2='1' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    30. ### INSERT INTO `xiaoboluo`.`test_load`
    31. ### SET
    32. ### @1=4 /* INT meta=0 nullable=0 is_null=0 */
    33. ### @2='2' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    34. ### INSERT INTO `xiaoboluo`.`test_load`
    35. ### SET
    36. ### @1=6 /* INT meta=0 nullable=0 is_null=0 */
    37. ### @2='null' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    38. ### INSERT INTO `xiaoboluo`.`test_load`
    39. ### SET
    40. ### @1=8 /* INT meta=0 nullable=0 is_null=0 */
    41. ### @2='4' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    42. # at 713
    43. #170504 11:18:57 server id 3306241 end_log_pos 744 CRC32 0x18b14b52 Xid = 1245
    44. COMMIT/*!*/;
    45. ......
  • 从上面解析binlog的结果中可以看到,数据写入成功,load data语句被转换为row格式记录在binlog中

  • 查看备库中数据是否正确复制

 
 
    1. mysql> use xiaoboluo
    2. Database changed
    3. mysql> select * from test_load;
    4. +----+------+
    5. | id | test |
    6. +----+------+
    7. | 2 | 1 |
    8. | 4 | 2 |
    9. | 6 | null |
    10. | 8 | 4 |
    11. +----+------+
    12. 4 rows in set (0.00 sec)
    1. [root@5f1772e3-0c7a-4537-97f9-9b57cf6a04c2 binlog]# ll
    2. total 196
    3. -rw-r----- 1 mysql mysql 4916 May 4 00:11 mysql-bin.000014
    4.  
    5. -rw-r----- 1 mysql mysql 4557 May 4 00:12 mysql-bin.000015
    6. -rw-r----- 1 mysql mysql 5595 May 4 09:39 mysql-bin.000016
    7. -rw-r----- 1 mysql mysql 366 May 4 09:41 mysql-bin.000017
    8. -rw-r----- 1 mysql mysql 744 May 4 09:51 mysql-bin.000018
    9.  
    10. -rw-r----- 1 mysql mysql 744 May 4 11:18 mysql-bin.000019
    11. -rw-r----- 1 mysql mysql 988 May 4 11:18 mysql-bin.index
    12.  
    13.  
    14. [root@5f1772e3-0c7a-4537-97f9-9b57cf6a04c2 binlog]# mysqlbinlog -vv --base64-output=decode-rows mysql-bin.000018
    15. # at 259
    16. #170504 11:18:51 server id 3306241 end_log_pos 354 CRC32 0x9d5985ad Query thread_id=155 exec_time=0 error_code=0
    17. use `xiaoboluo`/*!*/;
    18. ......
    19. truncate test_load
    20. ......
    21. BEGIN
    22. /*!*/;
    23. # at 501
    24. #170504 11:18:57 server id 3306241 end_log_pos 583 CRC32 0x0e8f7603 Rows_query
    25. # load data infile '/tmp/test_load.txt' into table test_load # 这里可以看到load data语句在这里,这里是开启了参数binlog_rows_query_log_events=ON之后记录的原生sql,默认被加了注释,主备复制不会执行
    26. # at 583
    27. #170504 11:18:57 server id 3306241 end_log_pos 643 CRC32 0xe1c5d4d0 Table_map: `xiaoboluo`.`test_load` mapped to number 341
    28. # at 643
    29. #170504 11:18:57 server id 3306241 end_log_pos 713 CRC32 0x31619df3 Write_rows: table id 341 flags: STMT_END_F
    30. ### INSERT INTO `xiaoboluo`.`test_load` #这里是用于主备复制的数据变更日志,可以看到在row格式下被转换为了row格式
    31. ### SET
    32. ### @1=2 /* INT meta=0 nullable=0 is_null=0 */
    33. ### @2='1' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    34. ### INSERT INTO `xiaoboluo`.`test_load`
    35. ### SET
    36. ### @1=4 /* INT meta=0 nullable=0 is_null=0 */
    37. ### @2='2' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    38. ### INSERT INTO `xiaoboluo`.`test_load`
    39. ### SET
    40. ### @1=6 /* INT meta=0 nullable=0 is_null=0 */
    41. ### @2='null' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    42. ### INSERT INTO `xiaoboluo`.`test_load`
    43. ### SET
    44. ### @1=8 /* INT meta=0 nullable=0 is_null=0 */
    45. ### @2='4' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    46. # at 713
    47. #170504 11:18:57 server id 3306241 end_log_pos 744 CRC32 0x18b14b52 Xid = 1245
    48. COMMIT/*!*/;
    49. ......
  • 解析备库binlog中是如何记录的load data语句
 
 
    1. [root@e710d318-d5b4-4bc7-a606-d09f06ff5f5d binlog]# ll
    2. total 100
    3. -rw-r----- 1 mysql mysql 990 May 1 01:36 mysql-bin.000001
    4. -rw-r----- 1 mysql mysql 54766 May 4 00:02 mysql-bin.000002
    5. -rw-r----- 1 mysql mysql 21376 May 4 09:40 mysql-bin.000003
    6. -rw-r----- 1 mysql mysql 401 May 4 09:50 mysql-bin.000004
    7. -rw-r----- 1 mysql mysql 730 May 4 09:51 mysql-bin.000005
    8. -rw-r----- 1 mysql mysql 730 May 4 11:18 mysql-bin.000006
    9. -rw-r----- 1 mysql mysql 312 May 4 11:18 mysql-bin.index
    10. [root@e710d318-d5b4-4bc7-a606-d09f06ff5f5d binlog]# mysqlbinlog -vv --base64-output=decode-rows mysql-bin.000009
    11. ......
    12. # at 259
    13. #170504 11:18:51 server id 3306241 end_log_pos 354 CRC32 0x9d5985ad Query thread_id=155 exec_time=0 error_code=0
    14. use `xiaoboluo`/*!*/;
    15. ......
    16. truncate test_load
    17. ......
    18. # at 487
    19. #170504 11:18:57 server id 3306241 end_log_pos 569 CRC32 0x97dd19e1 Rows_query
    20. # load data infile '/tmp/test_load.txt' into table test_load # 这里可以看到load data语句在这里,这里是开启了参数binlog_rows_query_log_events=ON之后记录的原生sql,默认被加了注释,主备复制不会执行
    21. # at 569
    22. #170504 11:18:57 server id 3306241 end_log_pos 629 CRC32 0x6bef4f90 Table_map: `xiaoboluo`.`test_load` mapped to number 302
    23. # at 629
    24. #170504 11:18:57 server id 3306241 end_log_pos 699 CRC32 0x5a86b7f1 Write_rows: table id 302 flags: STMT_END_F
    25. ### INSERT INTO `xiaoboluo`.`test_load` #这里是备库记录的主库binlog日志,可以看到在row格式下被转换为了row格式,与mixed格式下记录的内容相同
    26. ### SET
    27. ### @1=2 /* INT meta=0 nullable=0 is_null=0 */
    28. ### @2='1' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    29. ### INSERT INTO `xiaoboluo`.`test_load`
    30. ### SET
    31. ### @1=4 /* INT meta=0 nullable=0 is_null=0 */
    32. ### @2='2' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    33. ### INSERT INTO `xiaoboluo`.`test_load`
    34. ### SET
    35. ### @1=6 /* INT meta=0 nullable=0 is_null=0 */
    36. ### @2='null' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    37. ### INSERT INTO `xiaoboluo`.`test_load`
    38. ### SET
    39. ### @1=8 /* INT meta=0 nullable=0 is_null=0 */
    40. ### @2='4' /* VARSTRING(300) meta=300 nullable=1 is_null=0 */
    41. # at 699
    42. #170504 11:18:57 server id 3306241 end_log_pos 730 CRC32 0x983a4a33 Xid = 440
    43. COMMIT/*!*/;
    44. ......

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/28218939/viewspace-2139837/,如需转载,请注明出处,否则将追究法律责任。

转载于:http://blog.itpub.net/28218939/viewspace-2139837/

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值