File: kill-2.test

package info (click to toggle)
mariadb-10.0 10.0.32-0%2Bdeb8u1
  • links: PTS, VCS
  • area: main
  • in suites: jessie
  • size: 476,064 kB
  • sloc: cpp: 1,400,131; ansic: 832,140; perl: 54,391; sh: 41,304; pascal: 32,365; yacc: 14,921; xml: 5,257; sql: 4,667; cs: 4,647; makefile: 4,555; ruby: 4,465; python: 2,292; lex: 1,427; java: 941; asm: 295; awk: 54; php: 22; sed: 16
file content (29 lines) | stat: -rw-r--r-- 809 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
#
# Test KILL and KILL QUERY statements.
#
# Killing a connection in an embedded server does not work like in a normal
# server, if it is waiting for a new statement. In an embedded server, the
# connection does not read() from a socket, but returns control to the
# application. 'mysqltest' does not handle the kill request.
#

-- source include/not_embedded.inc
-- source include/not_threadpool.inc

--echo #
--echo # MDEV-6896 kill user command cause MariaDB crash!
--echo #

create user foo@'127.0.0.1';

--connect (con1,127.0.0.1,foo,,)

--connection default
select user from information_schema.processlist;
kill user foo@'127.0.0.1';

let $wait_condition=
    select count(*) = 0 from information_schema.processlist
    where user = "foo";
--source include/wait_condition.inc
drop user foo@'127.0.0.1';