KILL [CONNECTION | QUERY]
Each connection to mysqld runs in a separate
thread. You can kill a thread with the
Thread processlist identifiers can be determined from the
ID column of the
Id column of
SHOW PROCESSLIST output, and the
PROCESSLIST_ID column of the Performance
threads table. The value for
the current thread is returned by the
KILL permits an optional
terminates the statement the connection is currently
executing, but leaves the connection itself intact.
If you have the
privilege, you can see all threads. If you have the
SUPER privilege, you can kill all
threads and statements. Otherwise, you can see and kill only
your own threads and statements.
You cannot use
KILL with the
Embedded MySQL Server library because the embedded server
merely runs inside the threads of the host application. It
does not create any connection threads of its own.
When you use
thread-specific kill flag is set for the thread. In most cases,
it might take some time for the thread to die because the kill
flag is checked only at specific intervals:
SELECT operations, for
ORDER BY and
loops, the flag is checked after reading a block of rows. If
the kill flag is set, the statement is aborted.
operations, the kill flag is checked before each block of
rows are read from the original table. If the kill flag was
set, the statement is aborted and the temporary table is
DELETE operations, the kill
flag is checked after each block read and after each updated
or deleted row. If the kill flag is set, the statement is
aborted. If you are not using transactions, the changes are
not rolled back.
GET_LOCK() aborts and returns
INSERT DELAYED thread
quickly flushes (inserts) all rows it has in memory and then
If the thread is in the table lock handler (state:
Locked), the table lock is quickly
If the thread is waiting for free disk space in a write call, the write is aborted with a “disk full” error message.
Copyright © 1997, 2015, Oracle and/or its affiliates. All rights reserved. Legal Notices