2010-04-28 14:47:49 +02:00
call mtr.add_suppression("Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT");
2007-05-28 12:50:29 +02:00
CREATE TABLE t1m (m INT, n INT) ENGINE=MYISAM;
CREATE TABLE t1b (b INT, c INT) ENGINE=BLACKHOLE;
CREATE TABLE t1n (e INT, f INT) ENGINE=NDB;
2007-06-19 22:18:16 +02:00
RESET MASTER;
2007-05-28 12:50:29 +02:00
SET SESSION BINLOG_FORMAT=STATEMENT;
INSERT INTO t1b VALUES (1,1), (1,2), (2,1), (2,2);
2008-02-29 00:50:15 +03:00
INSERT INTO t1m VALUES (1,1), (1,2), (2,1), (2,2);
2007-05-28 12:50:29 +02:00
UPDATE t1m, t1b SET m = 2, b = 3 WHERE n = c;
2009-11-03 19:02:56 +00:00
The last event before the COMMIT is use `test`; UPDATE t1m, t1b SET m = 2, b = 3 WHERE n = c
2007-06-19 22:18:16 +02:00
*** Please look in binlog_multi_engine.test if you have a diff here ****
START TRANSACTION;
INSERT INTO t1n VALUES (1,1), (1,2), (2,1), (2,2);
2007-05-28 12:50:29 +02:00
UPDATE t1m, t1n SET m = 2, e = 3 WHERE n = f;
2009-11-03 19:02:56 +00:00
Warnings:
2010-06-02 00:25:08 +01:00
Note 1592 Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement accesses nontransactional table as well as transactional or temporary table, and writes to any of them.
2007-05-28 12:50:29 +02:00
UPDATE t1n, t1b SET e = 2, b = 3 WHERE f = c;
2007-06-19 22:18:16 +02:00
COMMIT;
2007-05-28 12:50:29 +02:00
TRUNCATE t1m;
TRUNCATE t1b;
TRUNCATE t1n;
2007-06-19 22:18:16 +02:00
show binlog events from <binlog_start>;
Log_name Pos Event_type Server_id End_log_pos Info
2009-05-31 13:44:41 +08:00
mysqld-bin.000001 # Query # # BEGIN
2008-01-11 16:56:14 +01:00
mysqld-bin.000001 # Query # # use `test`; INSERT INTO t1b VALUES (1,1), (1,2), (2,1), (2,2)
2009-05-31 13:44:41 +08:00
mysqld-bin.000001 # Query # # COMMIT
2009-11-03 19:02:56 +00:00
mysqld-bin.000001 # Query # # BEGIN
2008-03-25 18:40:49 +01:00
mysqld-bin.000001 # Query # # use `test`; INSERT INTO t1m VALUES (1,1), (1,2), (2,1), (2,2)
2009-11-03 19:02:56 +00:00
mysqld-bin.000001 # Query # # COMMIT
mysqld-bin.000001 # Query # # BEGIN
2008-01-11 16:56:14 +01:00
mysqld-bin.000001 # Query # # use `test`; UPDATE t1m, t1b SET m = 2, b = 3 WHERE n = c
2009-11-03 19:02:56 +00:00
mysqld-bin.000001 # Query # # COMMIT
2009-05-31 13:44:41 +08:00
mysqld-bin.000001 # Query # # BEGIN
Manual merge of patch for Bug#46364 from mysql-next-mr-bugfixing.
Conflicts:
- mysql-test/r/mysqld--help-win.result
- sql/sys_vars.cc
Original revsion (in next-mr-bugfixing):
------------------------------------------------------------
revno: 2971 [merge]
revision-id: alfranio.correia@sun.com-20100121210527-rbuheu5rnsmcakh1
committer: Alfranio Correia <alfranio.correia@sun.com>
branch nick: mysql-next-mr-bugfixing
timestamp: Thu 2010-01-21 21:05:27 +0000
message:
BUG#46364 MyISAM transbuffer problems (NTM problem)
It is well-known that due to concurrency issues, a slave can become
inconsistent when a transaction contains updates to both transaction and
non-transactional tables.
In a nutshell, the current code-base tries to preserve causality among the
statements by writing non-transactional statements to the txn-cache which
is flushed upon commit. However, modifications done to non-transactional
tables on behalf of a transaction become immediately visible to other
connections but may not immediately get into the binary log and therefore
consistency may be broken.
In general, it is impossible to automatically detect causality/dependency
among statements by just analyzing the statements sent to the server. This
happen because dependency may be hidden in the application code and it is
necessary to know a priori all the statements processed in the context of
a transaction such as in a procedure. Moreover, even for the few cases that
we could automatically address in the server, the computation effort
required could make the approach infeasible.
So, in this patch we introduce the option
- "--binlog-direct-non-transactional-updates" that can be used to bypass
the current behavior in order to write directly to binary log statements
that change non-transactional tables.
Besides, it is used to enable the WL#2687 which is disabled by default.
------------------------------------------------------------
revno: 2970.1.1
revision-id: alfranio.correia@sun.com-20100121131034-183r4qdyld7an5a0
parent: alik@sun.com-20100121083914-r9rz2myto3tkdya0
committer: Alfranio Correia <alfranio.correia@sun.com>
branch nick: mysql-next-mr-bugfixing
timestamp: Thu 2010-01-21 13:10:34 +0000
message:
BUG#46364 MyISAM transbuffer problems (NTM problem)
It is well-known that due to concurrency issues, a slave can become
inconsistent when a transaction contains updates to both transaction and
non-transactional tables.
In a nutshell, the current code-base tries to preserve causality among the
statements by writing non-transactional statements to the txn-cache which
is flushed upon commit. However, modifications done to non-transactional
tables on behalf of a transaction become immediately visible to other
connections but may not immediately get into the binary log and therefore
consistency may be broken.
In general, it is impossible to automatically detect causality/dependency
among statements by just analyzing the statements sent to the server. This
happen because dependency may be hidden in the application code and it is
necessary to know a priori all the statements processed in the context of
a transaction such as in a procedure. Moreover, even for the few cases that
we could automatically address in the server, the computation effort
required could make the approach infeasible.
So, in this patch we introduce the option
- "--binlog-direct-non-transactional-updates" that can be used to bypass
the current behavior in order to write directly to binary log statements
that change non-transactional tables.
Besides, it is used to enable the WL#2687 which is disabled by default.
2010-02-02 10:56:42 +03:00
mysqld-bin.000001 # Query # # use `test`; UPDATE t1n, t1b SET e = 2, b = 3 WHERE f = c
mysqld-bin.000001 # Query # # COMMIT
mysqld-bin.000001 # Query # # BEGIN
2008-01-11 16:56:14 +01:00
mysqld-bin.000001 # Query # # use `test`; INSERT INTO t1n VALUES (1,1), (1,2), (2,1), (2,2)
mysqld-bin.000001 # Query # # use `test`; UPDATE t1m, t1n SET m = 2, e = 3 WHERE n = f
2009-05-31 13:44:41 +08:00
mysqld-bin.000001 # Query # # COMMIT
2008-01-11 16:56:14 +01:00
mysqld-bin.000001 # Query # # BEGIN
mysqld-bin.000001 # Table_map # # table_id: # (test.t1n)
mysqld-bin.000001 # Table_map # # table_id: # (mysql.ndb_apply_status)
mysqld-bin.000001 # Write_rows # # table_id: # flags: STMT_END_F
mysqld-bin.000001 # Query # # COMMIT
2008-03-25 18:40:49 +01:00
mysqld-bin.000001 # Query # # use `test`; TRUNCATE t1m
mysqld-bin.000001 # Query # # use `test`; TRUNCATE t1b
2008-01-11 16:56:14 +01:00
mysqld-bin.000001 # Query # # use `test`; TRUNCATE t1n
2007-06-19 22:18:16 +02:00
RESET MASTER;
2007-05-28 12:50:29 +02:00
SET SESSION BINLOG_FORMAT=MIXED;
2008-03-26 07:22:42 +01:00
INSERT INTO t1b VALUES (1,1), (1,2), (2,1), (2,2);
2008-02-29 00:50:15 +03:00
INSERT INTO t1m VALUES (1,1), (1,2), (2,1), (2,2);
2009-11-03 19:02:56 +00:00
The last event before the COMMIT is use `test`; INSERT INTO t1m VALUES (1,1), (1,2), (2,1), (2,2)
2007-05-28 12:50:29 +02:00
INSERT INTO t1n VALUES (1,1), (1,2), (2,1), (2,2);
UPDATE t1m, t1b SET m = 2, b = 3 WHERE n = c;
UPDATE t1m, t1n SET m = 2, e = 3 WHERE n = f;
2010-04-28 14:47:49 +02:00
ERROR HY000: Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.
2007-05-28 12:50:29 +02:00
TRUNCATE t1m;
TRUNCATE t1b;
TRUNCATE t1n;
show binlog events from <binlog_start>;
Log_name Pos Event_type Server_id End_log_pos Info
2009-05-31 13:44:41 +08:00
mysqld-bin.000001 # Query # # BEGIN
2008-01-11 16:56:14 +01:00
mysqld-bin.000001 # Query # # use `test`; INSERT INTO t1b VALUES (1,1), (1,2), (2,1), (2,2)
2009-05-31 13:44:41 +08:00
mysqld-bin.000001 # Query # # COMMIT
2009-11-03 19:02:56 +00:00
mysqld-bin.000001 # Query # # BEGIN
2008-03-25 18:40:49 +01:00
mysqld-bin.000001 # Query # # use `test`; INSERT INTO t1m VALUES (1,1), (1,2), (2,1), (2,2)
2009-11-03 19:02:56 +00:00
mysqld-bin.000001 # Query # # COMMIT
2008-01-11 16:56:14 +01:00
mysqld-bin.000001 # Query # # BEGIN
mysqld-bin.000001 # Table_map # # table_id: # (test.t1n)
mysqld-bin.000001 # Table_map # # table_id: # (mysql.ndb_apply_status)
mysqld-bin.000001 # Write_rows # # table_id: #
mysqld-bin.000001 # Write_rows # # table_id: # flags: STMT_END_F
mysqld-bin.000001 # Query # # COMMIT
2010-06-30 16:25:13 +01:00
mysqld-bin.000001 # Query # # BEGIN
mysqld-bin.000001 # Query # # use `test`; UPDATE t1m, t1b SET m = 2, b = 3 WHERE n = c
mysqld-bin.000001 # Query # # COMMIT
2008-03-25 18:40:49 +01:00
mysqld-bin.000001 # Query # # use `test`; TRUNCATE t1m
mysqld-bin.000001 # Query # # use `test`; TRUNCATE t1b
2008-01-11 16:56:14 +01:00
mysqld-bin.000001 # Query # # use `test`; TRUNCATE t1n
2007-06-19 22:18:16 +02:00
RESET MASTER;
SET SESSION BINLOG_FORMAT=ROW;
INSERT INTO t1m VALUES (1,1), (1,2), (2,1), (2,2);
INSERT INTO t1b VALUES (1,1), (1,2), (2,1), (2,2);
INSERT INTO t1n VALUES (1,1), (1,2), (2,1), (2,2);
2007-06-22 01:39:23 +02:00
UPDATE t1m, t1n SET m = 2, e = 3 WHERE n = f;
2010-04-28 14:47:49 +02:00
ERROR HY000: Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.
2007-06-19 22:18:16 +02:00
UPDATE t1n, t1b SET e = 2, b = 3 WHERE f = c;
2010-04-28 14:47:49 +02:00
ERROR HY000: Cannot execute statement: impossible to write to binary log since more than one engine is involved and at least one engine is self-logging.
2007-06-19 22:18:16 +02:00
show binlog events from <binlog_start>;
Log_name Pos Event_type Server_id End_log_pos Info
2009-05-31 13:44:41 +08:00
mysqld-bin.000001 # Query # # BEGIN
2008-10-24 14:51:06 +02:00
mysqld-bin.000001 # Table_map # # table_id: # (test.t1m)
mysqld-bin.000001 # Write_rows # # table_id: # flags: STMT_END_F
2009-05-31 13:44:41 +08:00
mysqld-bin.000001 # Query # # COMMIT
mysqld-bin.000001 # Query # # BEGIN
2008-10-24 14:51:06 +02:00
mysqld-bin.000001 # Table_map # # table_id: # (test.t1b)
mysqld-bin.000001 # Write_rows # # table_id: # flags: STMT_END_F
2009-05-31 13:44:41 +08:00
mysqld-bin.000001 # Query # # COMMIT
2008-10-24 14:51:06 +02:00
mysqld-bin.000001 # Query # # BEGIN
mysqld-bin.000001 # Table_map # # table_id: # (test.t1n)
mysqld-bin.000001 # Table_map # # table_id: # (mysql.ndb_apply_status)
mysqld-bin.000001 # Write_rows # # table_id: #
mysqld-bin.000001 # Write_rows # # table_id: # flags: STMT_END_F
mysqld-bin.000001 # Query # # COMMIT
2007-06-19 22:18:16 +02:00
RESET MASTER;
DROP TABLE t1m, t1b, t1n;