mirror of
https://github.com/MariaDB/server.git
synced 2025-05-11 13:21:44 +03:00
41e0d0a3ab
The problem is that there is only one autoinc value associated with
the query when binlogging. If more than one autoinc values are used
in the query, the autoinc values after the first one can be inserted
wrongly on slave. So these autoinc values can become inconsistent on
master and slave.
The problem is resolved by marking all the statements that invoke
a trigger or call a function that updated autoinc fields as unsafe,
and will switch to row-format in Mixed mode. Actually, the statement
is safe if just one autoinc value is used in sub-statement, but it's
impossible to check how many autoinc values are used in sub-statement.)
mysql-test/suite/rpl/r/rpl_auto_increment_update_failure.result:
Test result for bug#45677
mysql-test/suite/rpl/t/rpl_auto_increment_update_failure.test:
Added test to verify the following two properties:
P1) insert/update in an autoinc column causes statement to
be logged in row format if binlog_format=mixed
P2) if binlog_format=mixed, and a trigger or function contains
two or more inserts/updates in a table that has an autoinc
column, then the slave should not go out of sync, even if
there are concurrent transactions.
sql/sql_base.cc:
Added function 'has_write_table_with_auto_increment' to check
if one (or more) write tables have auto_increment columns.
Removed function 'has_two_write_locked_tables_with_auto_increment',
because the function is included in function
'has_write_table_with_auto_increment'.
45 lines
1.4 KiB
Plaintext
45 lines
1.4 KiB
Plaintext
#
|
|
# This test verifies if inserting data into view that invokes a
|
|
# trigger will make the autoinc values become inconsistent on
|
|
# master and slave.
|
|
#
|
|
connection master;
|
|
CREATE TABLE t1(i1 int not null auto_increment, c1 INT, primary key(i1)) engine=innodb;
|
|
CREATE TABLE t2(i1 int not null auto_increment, c2 INT, primary key(i1)) engine=innodb;
|
|
CREATE TABLE t3(i1 int not null auto_increment, a int, primary key(i1)) engine=innodb;
|
|
eval create trigger tr16 $insert_action on t1 for each row insert into t3(a) values(new.c1);
|
|
eval create trigger tr17 $insert_action on t2 for each row insert into t3(a) values(new.c2);
|
|
begin;
|
|
INSERT INTO t1(c1) VALUES (11), (12);
|
|
INSERT INTO t2(c2) VALUES (13), (14);
|
|
|
|
CREATE VIEW v16 AS SELECT c1, c2 FROM t1, t2;
|
|
|
|
INSERT INTO v16(c1) VALUES (15),(16);
|
|
INSERT INTO v16(c2) VALUES (17),(18);
|
|
|
|
connection master1;
|
|
INSERT INTO v16(c1) VALUES (19),(20);
|
|
INSERT INTO v16(c2) VALUES (21),(22);
|
|
|
|
connection master;
|
|
INSERT INTO v16(c1) VALUES (23), (24);
|
|
INSERT INTO v16(c1) VALUES (25), (26);
|
|
commit;
|
|
sync_slave_with_master;
|
|
--echo #Test if the results are consistent on master and slave
|
|
--echo #for 'INSERT DATA INTO VIEW WHICH INVOKES TRIGGERS'
|
|
let $diff_table_1=master:test.t3;
|
|
let $diff_table_2=slave:test.t3;
|
|
source include/diff_tables.inc;
|
|
|
|
connection master;
|
|
DROP TABLE t1;
|
|
DROP TABLE t2;
|
|
DROP TABLE t3;
|
|
DROP VIEW v16;
|
|
sync_slave_with_master;
|
|
|
|
|
|
|