PGXC_STAT_ACTIVITY
PGXC_STAT_ACTIVITY displays information about the current user's queries on all CNs in the current cluster. Only users with the monitor admin or sysadmin permission can view the view.
Name |
Type |
Description |
---|---|---|
coorname |
text |
Name of a CN in the current cluster |
datid |
oid |
OID of the database that the user session connects to in the backend |
datname |
text |
Name of the database that the user session connects to in the backend |
pid |
bigint |
Process ID of the backend |
sessionid |
bigint |
Session ID |
usesysid |
oid |
OID of the user logged in to the backend |
usename |
text |
Name of the user logged in to the backend |
application_name |
text |
Name of the application connected to the backend |
client_addr |
inet |
IP address of the client connected to the backend. If this column is null, either the client is connected via a Unix socket on the server machine or this is an internal process such as autovacuum. |
client_hostname |
text |
Host name of the connected client, as reported by a reverse DNS lookup of client_addr. This column will be non-null for IP connections only when log_hostname is enabled. |
client_port |
integer |
TCP port number that the client uses for communication with the backend (–1 if a Unix socket is used) |
backend_start |
timestamp with time zone |
Time when this process was started, that is, when the client connected to the server |
xact_start |
timestamp with time zone |
Time when the current transaction was started (null if no transaction is active). If the current query is the first of its transaction, this column is equal to the query_start column. |
query_start |
timestamp with time zone |
Time when the currently active query was started, or if state is not active, when the last query was started |
state_change |
timestamp with time zone |
Time when the last status was changed |
waiting |
boolean |
Whether the backend is currently waiting on a lock. If it is, the value is true. Otherwise, the value is false. |
enqueue |
text |
Queuing status of a statement. Its value can be:
|
state |
text |
Backend status. Its value can be:
NOTE:
Only system administrators can view the session status of their accounts. The state information of other accounts is empty. For example, after user judy is connected to the database, the state information of user joe and the initial user omm in pgxc_stat_activity is empty. SELECT datname, usename, usesysid, state,pid FROM pgxc_stat_activity; datname | usename | usesysid | state | pid ----------+---------+----------+--------+----------------- postgres | omm | 10 | | 139968752121616 postgres | omm | 10 | | 139968903116560 db_tpcds | judy | 16398 | active | 139968391403280 postgres | omm | 10 | | 139968643069712 postgres | omm | 10 | | 139968680818448 postgres | joe | 16390 | | 139968563377936 (6 rows) |
resource_pool |
name |
Resource pool used by the user |
query_id |
bigint |
ID of a query |
query |
text |
Latest query at the backend. If state is active, this column shows the ongoing query. In all other states, it shows the last query that was executed. |
connection_info |
text |
A string in JSON format recording the driver type, driver version, driver deployment path, and process owner of the connected database. For details, see connection_info. |
global_sessionid |
text |
Global session ID |
unique_sql_id |
bigint |
Unique SQL statement ID |
trace_id |
text |
Driver-specific trace ID, which is associated with an application request |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot