mirror of
https://github.com/MariaDB/server.git
synced 2025-11-12 10:22:39 +03:00
(as part of the auto_increment cleanup of WL#3146; let's not be sad, that monster push still removed serious bugs): one problem with INSERT DELAYED (unexpected interval releases), one with stored functions (wrong auto_inc binlogging). These bugs were not released.
29 lines
1.1 KiB
Plaintext
29 lines
1.1 KiB
Plaintext
# Test of binlogging of INSERT_ID with INSERT DELAYED
|
|
create table t1 (a int not null auto_increment, primary key (a)) engine=myisam;
|
|
# First, avoid BUG#20627:
|
|
set @@session.auto_increment_increment=1, @@session.auto_increment_offset=1;
|
|
# Verify that only one INSERT_ID event is binlogged.
|
|
# Note, that because of WL#3368 mixed mode binlog records RBR events for the delayed
|
|
insert delayed into t1 values (207);
|
|
|
|
# We use sleeps between statements, that's the only way to get a
|
|
# repeatable binlog in a normal test run and under Valgrind. The
|
|
# reason is that without sleeps, rows of different INSERT DELAYEDs
|
|
# sometimes group together and sometimes not, so the table may be
|
|
# unlocked/relocked causing a different number of table map log
|
|
# events.
|
|
sleep 2;
|
|
insert delayed into t1 values (null);
|
|
sleep 2;
|
|
insert delayed into t1 values (300);
|
|
sleep 2; # time for the delayed queries to reach disk
|
|
insert delayed into t1 values (null),(null),(null),(null);
|
|
sleep 2;
|
|
insert delayed into t1 values (null),(null),(400),(null);
|
|
sleep 2;
|
|
select * from t1;
|
|
--replace_column 2 # 5 #
|
|
--replace_regex /table_id: [0-9]+/table_id: #/
|
|
show binlog events from 102;
|
|
drop table t1;
|