diff options
| author | unknown <elliot@mysql.com> | 2006-06-20 13:43:13 -0400 |
|---|---|---|
| committer | unknown <elliot@mysql.com> | 2006-06-20 13:43:13 -0400 |
| commit | b250722087ea2e99916c2b5bdfadbd51965f37cc (patch) | |
| tree | 6640c55b79e5bebb77e1a194bbade17b6cc55213 /mysql-test/r/lock_multi.result | |
| parent | 70a087e53daddaab806b39ad410ee9d026730e8f (diff) | |
| download | mariadb-git-b250722087ea2e99916c2b5bdfadbd51965f37cc.tar.gz | |
Applying patch from SergeyV
Fixes bug#17264, for alter table on win32 for successfull operation completion
it is used TL_WRITE(=10) lock instead of TL_WRITE_ALLOW_READ(=6), however here
in innodb handler TL_WRTIE is lifted to TL_WRITE_ALLOW_WRITE, which causes
race condition when several clients do alter table simultaneously.
mysql-test/r/lock_multi.result:
Test case for bug#17264.
mysql-test/t/lock_multi.test:
Test case for bug#17264
Diffstat (limited to 'mysql-test/r/lock_multi.result')
| -rw-r--r-- | mysql-test/r/lock_multi.result | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/mysql-test/r/lock_multi.result b/mysql-test/r/lock_multi.result index 2cb122fb988..2188d58e526 100644 --- a/mysql-test/r/lock_multi.result +++ b/mysql-test/r/lock_multi.result @@ -67,3 +67,9 @@ Select_priv N use test; use test; +create table t1 (f1 int(12) unsigned not null auto_increment, primary key(f1)) engine=innodb; +lock tables t1 write; + alter table t1 auto_increment=0; alter table t1 auto_increment=0; alter table t1 auto_increment=0; alter table t1 auto_increment=0; alter table t1 auto_increment=0; // + alter table t1 auto_increment=0; alter table t1 auto_increment=0; alter table t1 auto_increment=0; alter table t1 auto_increment=0; alter table t1 auto_increment=0; // +unlock tables; +drop table t1; |