- MySQL 5.1 Reference Manual :: 12 SQL Statement Syntax :: 12.4 Database Administration Statements :: 12.4.5 SHOW Syntax :: 12.4.5.31 SHOW PROCESSLIST Syntax
-
- MySQL 5.1 Reference Manual
- Preface, Notes, Licenses
- 1 General Information
- 2 Installing and Upgrading MySQL
- 3 Tutorial
- 4 MySQL Programs
- 5 MySQL Server Administration
- 6 Backup and Recovery
- 7 Optimization
- 8 Language Structure
- 9 Internationalization and Localization
- 10 Data Types
- 11 Functions and Operators
- 12 SQL Statement Syntax
- 13 Storage Engines
- 14 High Availability and Scalability
- 15 MySQL Enterprise Monitor
- 16 Replication
- 17 MySQL Cluster NDB 6.X/7.X
- 18 Partitioning
- 19 Stored Programs and Views
- 20 INFORMATION_SCHEMA Tables
- 21 Connectors and APIs
- 22 Extending MySQL
- A MySQL 5.1 Frequently Asked Questions
- B Errors, Error Codes, and Common Problems
- C MySQL Change History
- D Restrictions and Limits
- Index
- Standard Index
- C Function Index
- Command Index
- Function Index
- INFORMATION_SCHEMA Index
- Transaction Isolation Level Index
- JOIN Types Index
- Operator Index
- Option Index
- Privileges Index
- SQL Modes Index
- Status Variable Index
- Statement/Syntax Index
- System Variable Index
SHOW [FULL] PROCESSLIST
SHOW PROCESSLIST
shows you which threads are running. You can also get this information from theINFORMATION_SCHEMA
PROCESSLIST
table or the mysqladmin processlist command. If you have thePROCESS
privilege, you can see all 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 theFULL
keyword, only the first 100 characters of each statement are shown in theInfo
field.MySQL Enterprise. Subscribers to MySQL Enterprise Monitor receive instant notification and expert advice on resolution when there are too many concurrent processes. For more information, see http://www.mysql.com/products/enterprise/advisors.html.
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
SUPER
privilege, to ensure that administrators should always be able to connect and check the system (assuming that you are not giving this privilege to all your users).Threads can be killed with the
KILL
statement. See Section 12.4.6.4, “KILL
Syntax”.Here is an example of what
SHOW PROCESSLIST
output looks like: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 have the following meaning:
-
Id
The connection identifier.
-
User
The MySQL user who issued the statement. If this is
system user
, it refers to a nonclient thread spawned by the server to handle tasks internally. This could be the I/O or SQL thread used on replication slaves or a delayed-row handler.unauthenticated user
refers to a thread that has become associated with a client connection but for which authentication of the client user has not yet been done.event_scheduler
refers to the thread that monitors scheduled events. Forsystem user
orevent_scheduler
, there is no host specified in theHost
column. -
Host
The host name of the client issuing the statement (except for
system user
where there is no host).SHOW PROCESSLIST
reports the host name for TCP/IP connections in
format to make it easier to determine which client is doing what.host_name
:client_port
-
db
The default database, if one is selected, otherwise
NULL
. -
Command
The type of command the thread is executing. Descriptions for thread commands can be found at Section 7.5.6, “Examining Thread Information”. The value of this column corresponds to the
COM_
commands of the client/server protocol. See Section 5.1.6, “Server Status Variables”xxx
-
Time
The time in seconds that the thread has been in its current state.
-
State
An action, event, or state that indicates what the thread is doing. Descriptions for
State
values can be found at Section 7.5.6, “Examining Thread Information”.Most states correspond to very quick operations. If a thread stays in a given state for many seconds, there might be a problem that needs to be investigated.
For the
SHOW PROCESSLIST
statement, the value ofState
isNULL
. -
Info
The statement that the thread is executing, or
NULL
if it is not executing any statement. The statement might be the one sent to the server, or an innermost statement if the statement executes other statements. For example, if aCALL p1()
statement executes a stored procedurep1()
, and the procedure is executing aSELECT
statement, theInfo
value shows theSELECT
statement.