4
KILL [CONNECTION | QUERY] session_id
6
Calling KILL will terminate a either a running query, or disconnect a
7
connection, i.e. a session, from the database.
9
The way this works is that your connection sets a 'kill' flag in the session
10
you want to kill. At various points in query execution, a session will
11
check if the kill flag has been set, and if so, will quickly exit. So while
12
the KILL command will not strictly immediately kill the session, it should
13
appear to be fairly instantaneous.
15
Some engines such as Innobase will also check for the kill flag
16
during a lock wait, allowing you to kill a session waiting for a row lock.
4
Calling KILL will either terminate a running query, or disconnect a connection, i.e. a session, from the database. ::
6
KILL [CONNECTION | QUERY] session_id;
8
How it works: your connection sets a 'kill' flag in the session you want to kill. At various points in query execution, a session will check if the kill flag has been set, and if so, will quickly exit. (So while the KILL command doesn't technically kill the session immediately, it should appear to be fairly instantaneous.)
10
To kill the query being executed by a thread but leave the connection active, use the KILL QUERY command instead, followed by the appropriate thread ID.
12
Some engines such as Innobase will also check for the kill flag during a lock wait, allowing you to kill a session waiting for a row lock.
added
removed
docs/kill.rst
