mariadb/mysql-test/r/flush_read_lock_kill.result

SET @old_concurrent_insert= @@global.concurrent_insert;
SET @@global.concurrent_insert= 0;
DROP TABLE IF EXISTS t1;
CREATE TABLE t1 (kill_id INT);
INSERT INTO t1 VALUES(connection_id());
FLUSH TABLES WITH READ LOCK;
SELECT ((@id := kill_id) - kill_id) FROM t1;
((@id := kill_id) - kill_id)
0
KILL CONNECTION @id;
DROP TABLE t1;
SET @@global.concurrent_insert= @old_concurrent_insert;
Last slice of fix for Bug#42003 tests missing the disconnect of connections <> default + Fix for Bug#43114 wait_until_count_sessions too restrictive, random PB failures + Removal of a lot of other weaknesses found + modifications according to review 2009-03-03 21:34:18 +01:00			`SET @old_concurrent_insert= @@global.concurrent_insert;`
			`SET @@global.concurrent_insert= 0;`
			`DROP TABLE IF EXISTS t1;`
			`CREATE TABLE t1 (kill_id INT);`
			`INSERT INTO t1 VALUES(connection_id());`
			`FLUSH TABLES WITH READ LOCK;`
			`SELECT ((@id := kill_id) - kill_id) FROM t1;`
Making FLUSH TABLES WITH READ LOCK killable while it's waiting for running commits to finish. Normally this step is not long but it's still nice to be killable (especially in case of bug like BUG#6732 "FLUSH TABLES WITH READ LOCK + COMMIT makes next FLUSH...LOCK hang forever"). sql/lock.cc: making FLUSH TABLES WITH READ LOCK killable while it's waiting for running commits to finish sql/mysql_priv.h: prototype change sql/sql_parse.cc: now it's possible that make_global_read_lock_block_commit fails (killed) 2004-12-02 23:02:38 +01:00			`((@id := kill_id) - kill_id)`
			`0`
Last slice of fix for Bug#42003 tests missing the disconnect of connections <> default + Fix for Bug#43114 wait_until_count_sessions too restrictive, random PB failures + Removal of a lot of other weaknesses found + modifications according to review 2009-03-03 21:34:18 +01:00			`KILL CONNECTION @id;`
			`DROP TABLE t1;`
			`SET @@global.concurrent_insert= @old_concurrent_insert;`