mirror of
https://github.com/MariaDB/server.git
synced 2025-08-09 22:24:09 +03:00
5babac539d
the master but on the slave MySQL can decide to "downgrade" a INSERT DELAYED statement to normal insert in certain situations. One such situation is when the slave is replaying a replication feed. However INSERT DELAYED is logged even if there're no updates whereas the NORMAL INSERT is not logged in such cases. Fixed by always logging a "downgraded" INSERT DELAYED: even if there were no updates. mysql-test/r/rpl_insert_delayed.result: Bug #29571: test case mysql-test/t/rpl_insert_delayed.test: Bug #29571: test case sql/sql_insert.cc: Bug #29571: log INSERT DELAYED even if it was "downgraded" to INSERT (and there were no updates)
97 lines
2.5 KiB
Plaintext
97 lines
2.5 KiB
Plaintext
--source include/master-slave.inc
|
|
--source include/not_embedded.inc
|
|
--source include/not_windows.inc
|
|
|
|
connection master;
|
|
|
|
let $binlog_format_statement=1;
|
|
|
|
CREATE TABLE t1 (id INT primary key auto_increment, name VARCHAR(64));
|
|
|
|
sync_slave_with_master;
|
|
|
|
#
|
|
# BUG#26116 "If multi-row INSERT DELAYED has errors,
|
|
# statement-based binlogging breaks";
|
|
# happened only in statement-based binlogging.
|
|
#
|
|
|
|
connection master;
|
|
truncate table t1;
|
|
# first scenario: duplicate on first row
|
|
insert delayed into t1 values(10, "my name");
|
|
if ($binlog_format_statement)
|
|
{
|
|
# statement below will be converted to non-delayed INSERT and so
|
|
# will stop at first error, guaranteeing replication.
|
|
--error ER_DUP_ENTRY
|
|
insert delayed into t1 values(10, "is Bond"), (20, "James Bond");
|
|
}
|
|
if (!$binlog_format_statement)
|
|
{
|
|
insert delayed into t1 values(10, "is Bond"), (20, "James Bond");
|
|
}
|
|
flush table t1; # to wait for INSERT DELAYED to be done
|
|
select * from t1;
|
|
sync_slave_with_master;
|
|
# when bug existed in statement-based binlogging, t1 on slave had
|
|
# different content from on master
|
|
select * from t1;
|
|
|
|
# second scenario: duplicate on second row
|
|
connection master;
|
|
delete from t1 where id!=10;
|
|
if ($binlog_format_statement)
|
|
{
|
|
# statement below will be converted to non-delayed INSERT and so
|
|
# will be binlogged with its ER_DUP_ENTRY error code, guaranteeing
|
|
# replication (slave will hit the same error code and so be fine).
|
|
--error ER_DUP_ENTRY
|
|
insert delayed into t1 values(20, "is Bond"), (10, "James Bond");
|
|
}
|
|
if (!$binlog_format_statement)
|
|
{
|
|
insert delayed into t1 values(20, "is Bond"), (10, "James Bond");
|
|
}
|
|
flush table t1; # to wait for INSERT DELAYED to be done
|
|
select * from t1;
|
|
sync_slave_with_master;
|
|
# when bug existed in statement-based binlogging, query was binlogged
|
|
# with error_code=0 so slave stopped
|
|
select * from t1;
|
|
|
|
# clean up
|
|
connection master;
|
|
drop table t1;
|
|
sync_slave_with_master;
|
|
connection master;
|
|
|
|
#
|
|
# Bug #29571: INSERT DELAYED IGNORE written to binary log on the master but
|
|
# on the slave
|
|
#
|
|
CREATE TABLE t1(a int, UNIQUE(a));
|
|
INSERT DELAYED IGNORE INTO t1 VALUES(1);
|
|
INSERT DELAYED IGNORE INTO t1 VALUES(1);
|
|
|
|
#must show two INSERT DELAYED
|
|
--replace_column 1 x 2 x 3 x 4 x 5 x
|
|
show binlog events limit 11,100;
|
|
select * from t1;
|
|
|
|
sync_slave_with_master;
|
|
echo On slave;
|
|
#must show two INSERT DELAYED
|
|
--replace_column 1 x 2 x 3 x 4 x 5 x
|
|
show binlog events limit 12,100;
|
|
select * from t1;
|
|
|
|
|
|
# clean up
|
|
connection master;
|
|
drop table t1;
|
|
sync_slave_with_master;
|
|
connection master;
|
|
|
|
--echo End of 5.0 tests
|