• HOST 

The host name of the client issuing the statement (except for system user , for which there is no host). The host name for TCP/IP connections is reported in host_name : client_port  format to make it easier to determine which client is doing what. 

• DB 

The default database for the thread, or NULL  if none has been selected. 

• COMMAND 

The type of command the thread is executing on behalf of the client, or Sleep  if the session is idle. For descriptions of thread commands, see Section 8.14, “Examining Server Thread (Process) Information” . The value of this column corresponds to the COM_ xxx  commands of the client/server protocol and Com_ xxx  status variables. See Section 5.1.10, “Server Status Variables” . 

• TIME 

The time in seconds that the thread has been in its current state. For a replica SQL thread, the value is the number of seconds between the timestamp of the last replicated event and the real time of the replica host. See Section 17.2.3, “Replication Threads” . 

• STATE 

An action, event, or state that indicates what the thread is doing. For descriptions of STATE  values, see Section 8.14, “Examining Server Thread (Process) 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. 

• INFO 

The statement the thread is executing, or NULL  if it is executing no statement. The statement might be the one sent to the server, or an innermost statement if the statement executes other statements. For example, if a CALL  statement executes a stored procedure that is executing a SELECT  statement, the INFO  value shows the SELECT  statement. 

## Notes 

• PROCESSLIST  is a nonstandard INFORMATION_SCHEMA  table. 

•Like the output from the SHOW PROCESSLIST  statement, the PROCESSLIST  table provides information about all threads, even those belonging to other users, if you have the PROCESS  privilege. Otherwise (without the PROCESS  privilege), nonanonymous users have access to information about their own threads but not threads for other users, and anonymous users have no access to thread information. 

•If an SQL statement refers to the PROCESSLIST  table, MySQL populates the entire table once, when statement execution begins, so there is read consistency during the statement. There is no read consistency for a multi-statement transaction. 

The following statements are equivalent: 

SELECT * FROM INFORMATION_SCHEMA.PROCESSLIST SHOW FULL PROCESSLIST 

## 26.3.24 The INFORMATION_SCHEMA PROFILING Table 

