Browse Source
Bug #50407 mysqlbinlog --database=X produces bad output for SAVEPOINTs
Bug #50407 mysqlbinlog --database=X produces bad output for SAVEPOINTs
When mysqlbinlog was given the --database=X flag, it always printed 'ROLLBACK TO', but the corresponding 'SAVEPOINT' statement was not printed. The replicated filter(replicated-do/ignore-db) and binlog filter (binlog-do/ignore-db) has the same problem. They are solved in this patch together. After this patch, We always check whether the query is 'SAVEPOINT' statement or not. Because this is a literal check, 'SAVEPOINT' and 'ROLLBACK TO' statements are also binlogged in uppercase with no any comments. The binlog before this patch can be handled correctly except one case that any comments are in front of the keywords. for example: /* bla bla */ SAVEPOINT a; /* bla bla */ ROLLBACK TO a;pull/374/head
13 changed files with 243 additions and 32 deletions
-
4client/mysqlbinlog.cc
-
75mysql-test/r/mysqlbinlog.result
-
BINmysql-test/std_data/binlog_savepoint.000001
-
8mysql-test/suite/binlog/r/binlog_row_mix_innodb_myisam.result
-
8mysql-test/suite/binlog/r/binlog_stm_mix_innodb_myisam.result
-
62mysql-test/suite/rpl/r/rpl_begin_commit_rollback.result
-
2mysql-test/suite/rpl/r/rpl_innodb_mixed_dml.result
-
1mysql-test/suite/rpl/t/rpl_begin_commit_rollback-master.opt
-
51mysql-test/suite/rpl/t/rpl_begin_commit_rollback.test
-
11mysql-test/t/mysqlbinlog.test
-
26sql/log.cc
-
5sql/log_event.cc
-
22sql/log_event.h
@ -0,0 +1 @@ |
|||
--innodb --binlog-ignore-db=db2 |
Write
Preview
Loading…
Cancel
Save
Reference in new issue