mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 13:32:33 +01:00
884663662b
(back to behaviour of 4.1.7). Warning was not fatal: mysqldump continued. And the good thing is that it helped spot that starting from 4.1.7, SHOW CREATE DATABASE failed (if --single-transaction and first db has non-empty InnoDB table and there is a second db) and thus mysqldump produced CREATE DATABASE statements missing the CHARACTER SET clause. Removing the bug which was in the server, and the warning reporting in mysqldump (compatibility with old servers).
74 lines
1.5 KiB
Text
74 lines
1.5 KiB
Text
# Let's see if FLUSH TABLES WITH READ LOCK blocks COMMIT of existing
|
|
# transactions.
|
|
# We verify that we did not introduce a deadlock.
|
|
# This is intended to mimick how mysqldump and innobackup work.
|
|
|
|
-- source include/have_innodb.inc
|
|
|
|
connect (con1,localhost,root,,);
|
|
connect (con2,localhost,root,,);
|
|
connect (con3,localhost,root,,);
|
|
connection con1;
|
|
|
|
--disable_warnings
|
|
drop table if exists t1;
|
|
--enable_warnings
|
|
create table t1 (a int) engine=innodb;
|
|
|
|
# blocks COMMIT ?
|
|
|
|
begin;
|
|
insert into t1 values(1);
|
|
connection con2;
|
|
flush tables with read lock;
|
|
select * from t1;
|
|
connection con1;
|
|
send commit; # blocked by con2
|
|
sleep 1;
|
|
connection con2;
|
|
select * from t1; # verify con1 was blocked and data did not move
|
|
unlock tables;
|
|
connection con1;
|
|
reap;
|
|
|
|
# No deadlock ?
|
|
|
|
connection con1;
|
|
begin;
|
|
select * from t1 for update;
|
|
connection con2;
|
|
begin;
|
|
send select * from t1 for update; # blocked by con1
|
|
sleep 1;
|
|
connection con3;
|
|
send flush tables with read lock; # blocked by con2
|
|
connection con1;
|
|
commit; # should not be blocked by con3
|
|
connection con2;
|
|
reap;
|
|
connection con3;
|
|
reap;
|
|
unlock tables;
|
|
|
|
# BUG#6732 FLUSH TABLES WITH READ LOCK + COMMIT hangs later FLUSH TABLES
|
|
# WITH READ LOCK
|
|
|
|
connection con2;
|
|
commit; # unlock InnoDB row locks to allow insertions
|
|
connection con1;
|
|
begin;
|
|
insert into t1 values(10);
|
|
flush tables with read lock;
|
|
commit;
|
|
unlock tables;
|
|
connection con2;
|
|
flush tables with read lock; # bug caused hang here
|
|
unlock tables;
|
|
|
|
# BUG#7358 SHOW CREATE DATABASE fails if open transaction
|
|
|
|
begin;
|
|
select * from t1;
|
|
show create database test;
|
|
|
|
drop table t1;
|