A newer version of this documentation is available. Use the version menu above to view the most up-to-date release of the Greenplum 6.x documentation.


The view pg_stat_activity shows one row per server process with details about the associated user session and query. The columns that report data on the current query are available unless the parameter stats_command_string has been turned off. Furthermore, these columns are only visible if the user examining the view is a superuser or the same as the user owning the process being reported on.

The maximum length of the query text string stored in the column query can be controlled with the server configuration parameter track_activity_query_size.

Table 1. pg_catalog.pg_stat_activity
column type references description
datid oid pg_database.oid Database OID
datname name   Database name
pid integer   Process ID of this backend
sess_id integer   Session ID
usesysid oid pg_authid.oid OID of the user logged into this backend
usename name   Name of the user logged into this backend
application_name text   Name of the application that is connected to this backend
client_addr inet   IP address of the client connected to this backend. If this field is null, it indicates either that the client is connected via a Unix socket on the server machine or that 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 field will only be non-null for IP connections, and only when log_hostname is enabled.
client_port integer   TCP port number that the client is using for communication with this backend, or -1 if a Unix socket is used
backend_start timestamptz   Time backend process was started
xact_start timestamptz   Transaction start time
query_start timestamptz   Time query began execution
state_change timestampz   Time when the state was last changed
waiting boolean   True if waiting on a lock, false if not waiting
state text   Current overall state of this backend. Possible values are:
  • 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 is not currently executing a query.

  • idle in transaction (aborted): This state is similar to idle in transaction, except one of the statements in the transaction caused an error.

  • fastpath function call: The backend is executing a fast-path function.

  • disabled: This state is reported if track_activities is disabled in this backend.

query text   Text of this backend's most recent query. If state is active this field shows the currently executing query. In all other states, it shows the last query that was executed.
waiting_reason text   Reason the server process is waiting. The value can be:

lock, replication, or resgroup

rsgid oid pg_resgroup.oid Resource group OID or 0.

See Note.

rsgname text pg_resgroup.rsgname Resource group name or unknown.

See Note.

rsgqueueduration interval   For a queued query, the total time the query has been queued.
Note: When resource groups are enabled. Only query dispatcher (QD) processes will have a rsgid and rsgname. Other server processes such as a query executer (QE) process or session connection processes will have a rsgid value of 0 and a rsgname value of unknown. QE processes are managed by the same resource group as the dispatching QD process.