~drizzle-trunk/drizzle/development

#

# Tests for various concurrency-related aspects of ALTER TABLE implemetation

#

# This test takes rather long time so let us run it only in --big-test mode

--source include/big_test.inc

# Also we are using SBR to check that statements are executed

# in proper order.

--source include/have_binlog_format_mixed_or_statement.inc

#

# Test for bug #25044 "ALTER TABLE ... ENABLE KEYS acquires global

# 'opening tables' lock".

#

# ALTER TABLE ... ENABLE KEYS should not acquire LOCK_open mutex for

# the whole its duration as it prevents other queries from execution.

--disable_warnings

drop table if exists t1, t2;

--enable_warnings

connect (addconroot, localhost, root,,);

connection default;

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);

# Starting from 5.1 we have runtime settable @@debug variable,

# which can be used for introducing delays at certain points of

# statement execution, so we don't need many rows in 't1' to make

# this test repeatable.

alter table t1 disable keys;

insert into t1 values (RAND()*1000, RAND()*1000, RAND()*1000);

# Later we use binlog to check the order in which statements are

# executed so let us reset it first.

reset master;

--send alter table t1 enable keys;

connection addconroot;

--sleep 2

# This statement should not be blocked by in-flight ALTER and therefore

# should be executed and written to binlog before ALTER TABLE ... ENABLE KEYS

# finishes.

insert into t2 values (1);

# And this should wait until the end of ALTER TABLE ... ENABLE KEYS.

insert into t1 values (1, 1, 1);

connection default;

--reap

# Check that statements were executed/binlogged in correct order.

--replace_column 2 # 5 #

show binlog events in 'master-bin.000001' from 106;

# Clean up

drop tables t1, t2;

--echo End of 5.0 tests

#

# Additional coverage for the main ALTER TABLE case

#

# We should be sure that table being altered is properly

# locked during statement execution and in particular that

# no DDL or DML statement can sneak in and get access to

# the table when real operation has already taken place

# but this fact has not been noted in binary log yet.

--disable_warnings

drop table if exists t1, t2, t3;

--enable_warnings

create table t1 (i int);

# We are going to check that statements are logged in correct order

reset master;

--send alter table t1 change i c char(10) default 'Test1';

connection addconroot;

--sleep 2

insert into t1 values ();

select * from t1;

connection default;

--reap

--send alter table t1 change c vc varchar(100) default 'Test2';

connection addconroot;

--sleep 2

rename table t1 to t2;

connection default;

--reap

drop table t2;

# And now tests for ALTER TABLE with RENAME clause. In this

# case target table name should be properly locked as well.

create table t1 (i int);

--send alter table t1 change i c char(10) default 'Test3', rename to t2;

connection addconroot;

--sleep 2

insert into t2 values ();

select * from t2;

connection default;

--reap

--send alter table t2 change c vc varchar(100) default 'Test2', rename to t1;

connection addconroot;

--sleep 2

rename table t1 to t3;

connection default;

--reap

drop table t3;

# Check that all statements were logged in correct order

--replace_column 2 # 5 #

show binlog events in 'master-bin.000001' from 106;

--echo End of 5.1 tests