Oracle 5.0 Reference Manual page 1209

threads. Otherwise, you can see only your own threads (that is, threads associated with the MySQL
account that you are using). If you do not use the
statement are shown in the
This statement is very useful if you get the "too many connections" error message and want to find
out what is going on. MySQL reserves one extra connection to be used by accounts that have the
[578] privilege, to ensure that administrators should always be able to connect and check the
SUPER
system (assuming that you are not giving this privilege to all your users).
Threads can be killed with the
Here is an example of
SHOW PROCESSLIST
mysql> SHOW FULL PROCESSLIST\G
*************************** 1. row ***************************
Id: 1
User: system user
Host:
db: NULL
Command: Connect
Time: 1030455
State: Waiting for master to send event
Info: NULL
*************************** 2. row ***************************
Id: 2
User: system user
Host:
db: NULL
Command: Connect
Time: 1004
State: Has read all relay log; waiting for the slave
I/O thread to update it
Info: NULL
*************************** 3. row ***************************
Id: 3112
User: replikator
Host: artemis:2204
db: NULL
Command: Binlog Dump
Time: 2144
State: Has sent all binlog to slave; waiting for binlog to be updated
Info: NULL
*************************** 4. row ***************************
Id: 3113
User: replikator
Host: iconnect2:45781
db: NULL
Command: Binlog Dump
Time: 2086
State: Has sent all binlog to slave; waiting for binlog to be updated
Info: NULL
*************************** 5. row ***************************
Id: 3123
User: stefan
Host: localhost
db: apollon
Command: Query
Time: 0
State: NULL
Info: SHOW FULL PROCESSLIST
5 rows in set (0.00 sec)
The columns produced by
•
Id
The connection identifier.
•
User
Syntax
SHOW
field.
Info
statement. See
KILL
output:
have the following meanings:
SHOW PROCESSLIST
1189
keyword, only the first 100 characters of each
FULL
Section 13.7.6.3, "KILL Syntax".