mirror of
https://github.com/MariaDB/server.git
synced 2025-11-03 14:33:32 +03:00
8b1609a637
duplicate key entries on slave" (two concurrrent connections doing multi-row INSERT DELAYED to insert into an auto_increment column, caused replication slave to stop with "duplicate key error" (and binlog was wrong)), and BUG#26116 "If multi-row INSERT DELAYED has errors, statement-based binlogging breaks" (the binlog was not accounting for all rows inserted, or slave could stop). The fix is that: if (statement-based) binlogging is on, a multi-row INSERT DELAYED is silently converted to a non-delayed INSERT. Note: it is not possible to test BUG#25507 in 5.0 (requires mysqlslap), so it is tested only in the changeset for 5.1. However, BUG#26116 is tested here, and the fix for BUG#25507 is the same code change.
32 lines
752 B
Plaintext
32 lines
752 B
Plaintext
stop slave;
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
reset master;
|
|
reset slave;
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
start slave;
|
|
CREATE TABLE t1 (id INT primary key auto_increment, name VARCHAR(64));
|
|
truncate table t1;
|
|
insert delayed into t1 values(10, "my name");
|
|
insert delayed into t1 values(10, "is Bond"), (20, "James Bond");
|
|
ERROR 23000: Duplicate entry '10' for key 1
|
|
flush table t1;
|
|
select * from t1;
|
|
id name
|
|
10 my name
|
|
select * from t1;
|
|
id name
|
|
10 my name
|
|
delete from t1 where id!=10;
|
|
insert delayed into t1 values(20, "is Bond"), (10, "James Bond");
|
|
ERROR 23000: Duplicate entry '10' for key 1
|
|
flush table t1;
|
|
select * from t1;
|
|
id name
|
|
10 my name
|
|
20 is Bond
|
|
select * from t1;
|
|
id name
|
|
10 my name
|
|
20 is Bond
|
|
drop table t1;
|