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. Three columns are added to version 505.0.0. During the gray upgrade observation period, an error is reported. You need to use PG_STAT_ACTIVITY to directly connect to the target node for query. For details about the columns, see Table 1.

**Table 1** PGXC_STAT_ACTIVITY columns
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	Backend thread ID.
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	Specifies whether the backend is currently waiting for a lock. If yes, the value is true. Otherwise, the value is false. If a lock is being waited for on a DN, determine the DN based on the wait_status column in the pg_thread_wait_status view and query the waiting column in pg_stat_activity on the DN to check whether a lock wait occurs.
enqueue	text	Queuing status of a statement. Its value can be: waiting in queue: The statement is in the queue. Empty: The statement is running.
state	text	Backend status. Its value can be: active: The backend is executing a query. idle: The backend is waiting for a new client command. idle in transaction: The backend is in a transaction, but there is no statement being executed in the transaction. idle in transaction (aborted): The backend is in a transaction, but there are statements failed in the transaction. fastpath function call: The backend is executing a fast-path function. disabled: This state is reported if track_activities is disabled in this backend. 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 ----------+---------+----------+--------+----------------- testdb \| omm \| 10 \| \| 139968752121616 testdb \| omm \| 10 \| \| 139968903116560 db_tpcds \| judy \| 16398 \| active \| 139968391403280 testdb \| omm \| 10 \| \| 139968643069712 testdb \| omm \| 10 \| \| 139968680818448 testdb \| joe \| 16390 \| \| 139968563377936 (6 rows)
resource_pool	name	Resource pool used by the user
query_id	bigint	ID of a query statement.
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 the GUC parameter 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.
top_xid	xid	Top-level transaction ID of a transaction.
current_xid	xid	Current transaction ID of a transaction.
xlog_quantity	bigint	Amount of Xlogs currently used by a transaction, in bytes.