From 56c323c10f4e37318255c9d386e650e1513322e1 Mon Sep 17 00:00:00 2001 From: Sergei Golubchik Date: Mon, 19 Jan 2015 14:07:41 +0100 Subject: MDEV-6728 KILL QUERY executed on an idle connection can interrupt the next query reset KILL_QUERY when a new query execution is just about to be started --- mysql-test/r/kill_processlist-6619.result | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'mysql-test/r/kill_processlist-6619.result') diff --git a/mysql-test/r/kill_processlist-6619.result b/mysql-test/r/kill_processlist-6619.result index 588c8e6d139..8cb9fe7270c 100644 --- a/mysql-test/r/kill_processlist-6619.result +++ b/mysql-test/r/kill_processlist-6619.result @@ -3,10 +3,12 @@ SHOW PROCESSLIST; Id User Host db Command Time State Info Progress # root # test Sleep # # NULL 0.000 # root # test Query # # SHOW PROCESSLIST 0.000 +SET DEBUG_SYNC='before_execute_sql_command WAIT_FOR go'; +SHOW PROCESSLIST; connection default; KILL QUERY con_id; +SET DEBUG_SYNC='now SIGNAL go'; connection con1; -SHOW PROCESSLIST; ERROR 70100: Query execution was interrupted SHOW PROCESSLIST; Id User Host db Command Time State Info Progress -- cgit v1.2.1