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;
Bug#34891 sp_notembedded.test fails sporadically The problem is that since MyISAM's concurrent_insert is on by default some concurrent SELECT statements might not see changes made by INSERT statements in other connections, even if the INSERT statement has returned. The solution is to disable concurrent_insert so that INSERT statements returns after the data is actually visible to other statements. 2008-03-13 18:54:29 +01:00			`set @old_concurrent_insert= @@global.concurrent_insert;`
Fix for team tree failure. Synchronously wait for the query state to reach the desired value. 2008-02-27 22:08:29 +01:00			`set @@global.concurrent_insert= 0;`
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"). 2004-12-02 23:02:38 +01:00			`drop table if exists t1;`
			`create table t1 (kill_id int);`
			`insert into t1 values(connection_id());`
Update tests and result files after running with new mysqltest that better detects problems with test files 2006-10-04 13:09:37 +02:00			`flush tables with read lock;`
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"). 2004-12-02 23:02:38 +01:00			`select ((@id := kill_id) - kill_id) from t1;`
			`((@id := kill_id) - kill_id)`
			`0`
			`kill connection @id;`
			`drop table t1;`
Bug#34891 sp_notembedded.test fails sporadically The problem is that since MyISAM's concurrent_insert is on by default some concurrent SELECT statements might not see changes made by INSERT statements in other connections, even if the INSERT statement has returned. The solution is to disable concurrent_insert so that INSERT statements returns after the data is actually visible to other statements. 2008-03-13 18:54:29 +01:00			`set @@global.concurrent_insert= @old_concurrent_insert;`