mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 13:32:33 +01:00
7b1a94ef78
tables' lock." Execution of ALTER TABLE ... ENABLE KEYS on a table (which can take rather long time) prevented concurrent execution of all statements using tables. The problem was caused by the fact that we were holding LOCK_open mutex during whole duration of this statement and particularly during call to handler::enable_indexes(). This behavior was introduced as part of the fix for bug 14262 "SP: DROP PROCEDURE|VIEW (maybe more) write to binlog too late (race cond)" The patch simply restores old behavior. Note that we can safely do this as this operation takes exclusive lock (similar to name-lock) which blocks both DML and DDL on the table being altered. It also introduces mysql-test/include/wait_show_pattern.inc helper script which is used to make test-case for this bug robust enough.
18 lines
632 B
Text
18 lines
632 B
Text
drop table if exists t1, t2;
|
|
create table t1 (n1 int, n2 int, n3 int,
|
|
key (n1, n2, n3),
|
|
key (n2, n3, n1),
|
|
key (n3, n1, n2));
|
|
create table t2 (i int);
|
|
alter table t1 disable keys;
|
|
reset master;
|
|
alter table t1 enable keys;;
|
|
insert into t2 values (1);
|
|
insert into t1 values (1, 1, 1);
|
|
show binlog events in 'master-bin.000001' from 98;
|
|
Log_name Pos Event_type Server_id End_log_pos Info
|
|
master-bin.000001 # Query 1 # use `test`; insert into t2 values (1)
|
|
master-bin.000001 # Query 1 # use `test`; alter table t1 enable keys
|
|
master-bin.000001 # Query 1 # use `test`; insert into t1 values (1, 1, 1)
|
|
drop tables t1, t2;
|
|
End of 5.0 tests
|