pg_stat_activity

字段

PostgreSQL 18 的 22 个字段，按定义顺序排列。说明默认用本站手册的译文，没有译文的按英文原文显示。

演化历史

相邻两个大版本之间的差异，新的在前。版本号链到该版的字段表。

1. PostgreSQL 18 ← 17 仅描述更新

   1 处描述更新

   • backend_xid Top-level transaction identifier of this backend, if any; see Section 66.1. Top-level transaction identifier of this backend, if any; see Section 67.1.

2. PostgreSQL 17 ← 16 仅描述更新

   关系说明更新

   4 处描述更新

   • backend_type Type of current backend. Possible types are autovacuum launcher, autovacuum worker, logical replication launcher, logical replication worker, parallel worker, background writer, client backend, checkpointer, archiver, standalone backend, startup, walreceiver, walsender and walwriter. In addition, background workers registered by extensions may have additional types. Type of current backend. Possible types are autovacuum launcher, autovacuum worker, logical replication launcher, logical replication worker, parallel worker, background writer, client backend, checkpointer, archiver, standalone backend, startup, walreceiver, walsender, walwriter and walsummarizer. In addition, background workers registered by extensions may have additional types.
   • backend_xid Top-level transaction identifier of this backend, if any; see Section 74.1. Top-level transaction identifier of this backend, if any; see Section 66.1.
   • wait_event Wait event name if backend is currently waiting, otherwise NULL. See Table 28.5 through Table 28.13. Wait event name if backend is currently waiting, otherwise NULL. See Table 27.5 through Table 27.13.
   • wait_event_type The type of event for which the backend is waiting, if any; otherwise NULL. See Table 28.4. The type of event for which the backend is waiting, if any; otherwise NULL. See Table 27.4.

3. PostgreSQL 16 ← 15 仅描述更新

   3 处描述更新

   • backend_type Type of current backend. Possible types are autovacuum launcher, autovacuum worker, logical replication launcher, logical replication worker, parallel worker, background writer, client backend, checkpointer, archiver, startup, walreceiver, walsender and walwriter. In addition, background workers registered by extensions may have additional types. Type of current backend. Possible types are autovacuum launcher, autovacuum worker, logical replication launcher, logical replication worker, parallel worker, background writer, client backend, checkpointer, archiver, standalone backend, startup, walreceiver, walsender and walwriter. In addition, background workers registered by extensions may have additional types.
   • backend_xid Top-level transaction identifier of this backend, if any. Top-level transaction identifier of this backend, if any; see Section 74.1.
   • leader_pid Process ID of the parallel group leader, if this process is a parallel query worker. NULL if this process is a parallel group leader or does not participate in parallel query. Process ID of the parallel group leader if this process is a parallel query worker, or process ID of the leader apply worker if this process is a parallel apply worker. NULL indicates that this process is a parallel group leader or leader apply worker, or does not participate in any parallel operation.

4. PostgreSQL 14 ← 13 结构变更

   +query_id

   3 处描述更新

   • backend_type Type of current backend. Possible types are autovacuum launcher, autovacuum worker, logical replication launcher, logical replication worker, parallel worker, background writer, client backend, checkpointer, startup, walreceiver, walsender and walwriter. In addition, background workers registered by extensions may have additional types. Type of current backend. Possible types are autovacuum launcher, autovacuum worker, logical replication launcher, logical replication worker, parallel worker, background writer, client backend, checkpointer, archiver, startup, walreceiver, walsender and walwriter. In addition, background workers registered by extensions may have additional types.
   • wait_event Wait event name if backend is currently waiting, otherwise NULL. See Table 27.5 through Table 27.13. Wait event name if backend is currently waiting, otherwise NULL. See Table 28.5 through Table 28.13.
   • wait_event_type The type of event for which the backend is waiting, if any; otherwise NULL. See Table 27.4. The type of event for which the backend is waiting, if any; otherwise NULL. See Table 28.4.

5. PostgreSQL 13 ← 12 结构变更

   +leader_pid 关系说明更新

   4 处描述更新

   • client_port TCP port number that the client is using for communication with this backend, or -1 if a Unix socket is used TCP port number that the client is using for communication with this backend, or -1 if a Unix socket is used. If this field is null, it indicates that this is an internal server process.
   • state 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. Current overall state of this backend. Possible values are:
   • wait_event Wait event name if backend is currently waiting, otherwise NULL. See Table 27.4 for details. Wait event name if backend is currently waiting, otherwise NULL. See Table 27.5 through Table 27.13.
   • wait_event_type The type of event for which the backend is waiting, if any; otherwise NULL. Possible values are: LWLock: The backend is waiting for a lightweight lock. Each such lock protects a particular data structure in shared memory. wait_event will contain a name identifying the purpose of the lightweight lock. (Some locks have specific names; others are part of a group of locks each with a similar purpose.) Lock: The backend is waiting for a heavyweight lock. Heavyweight locks, also known as lock manager locks or simply locks, primarily protect SQL-visible objects such as tables. However, they are also used to ensure mutual exclusion for certain internal operations such as relation extension. wait_event will identify the type of lock awaited. BufferPin: The server process is waiting to access to a data buffer during a period when no other process can be examining that buffer. Buffer pin waits can be protracted if another process holds an open cursor which last read data from the buffer in question. Activity: The server process is idle. This is used by system processes waiting for activity in their main processing loop. wait_event will identify the specific wait point. Extension: The server process is waiting for activity in an extension module. This category is useful for modules to track custom waiting points. Client: The server process is waiting for some activity on a socket from user applications, and that the server expects something to happen that is independent from its internal processes. wait_event will identify the specific wait point. IPC: The server process is waiting for some activity from another process in the server. wait_event will identify the specific wait point. Timeout: The server process is waiting for a timeout to expire. wait_event will identify the specific wait point. IO: The server process is waiting for a IO to complete. wait_event will identify the specific wait point. The type of event for which the backend is waiting, if any; otherwise NULL. See Table 27.4.

6. PostgreSQL 12 ← 11 仅描述更新

   关系说明更新

   1 处描述更新

   • wait_event Wait event name if backend is currently waiting, otherwise NULL. See Table 28.4 for details. Wait event name if backend is currently waiting, otherwise NULL. See Table 27.4 for details.

7. PostgreSQL 11 ← 10 仅描述更新

   1 处描述更新

   • backend_type Type of current backend. Possible types are autovacuum launcher, autovacuum worker, background worker, background writer, client backend, checkpointer, startup, walreceiver, walsender and walwriter. Type of current backend. Possible types are autovacuum launcher, autovacuum worker, logical replication launcher, logical replication worker, parallel worker, background writer, client backend, checkpointer, startup, walreceiver, walsender and walwriter. In addition, background workers registered by extensions may have additional types.

8. PostgreSQL 10 ← 9.6 结构变更

   +backend_type 关系说明更新

   4 处描述更新

   • backend_start Time when this process was started, i.e., when the client connected to the server Time when this process was started. For client backends, this is the time the client connected to the server.
   • query 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. 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. By default the query text is truncated at 1024 bytes; this value can be changed via the parameter track_activity_query_size.
   • wait_event Wait event name if backend is currently waiting, otherwise NULL. See Table 28-4 for details. Wait event name if backend is currently waiting, otherwise NULL. See Table 28.4 for details.
   • wait_event_type The type of event for which the backend is waiting, if any; otherwise NULL. Possible values are: LWLockNamed: The backend is waiting for a specific named lightweight lock. Each such lock protects a particular data structure in shared memory. wait_event will contain the name of the lightweight lock. LWLockTranche: The backend is waiting for one of a group of related lightweight locks. All locks in the group perform a similar function; wait_event will identify the general purpose of locks in that group. Lock: The backend is waiting for a heavyweight lock. Heavyweight locks, also known as lock manager locks or simply locks, primarily protect SQL-visible objects such as tables. However, they are also used to ensure mutual exclusion for certain internal operations such as relation extension. wait_event will identify the type of lock awaited. BufferPin: The server process is waiting to access to a data buffer during a period when no other process can be examining that buffer. Buffer pin waits can be protracted if another process holds an open cursor which last read data from the buffer in question. The type of event for which the backend is waiting, if any; otherwise NULL. Possible values are: LWLock: The backend is waiting for a lightweight lock. Each such lock protects a particular data structure in shared memory. wait_event will contain a name identifying the purpose of the lightweight lock. (Some locks have specific names; others are part of a group of locks each with a similar purpose.) Lock: The backend is waiting for a heavyweight lock. Heavyweight locks, also known as lock manager locks or simply locks, primarily protect SQL-visible objects such as tables. However, they are also used to ensure mutual exclusion for certain internal operations such as relation extension. wait_event will identify the type of lock awaited. BufferPin: The server process is waiting to access to a data buffer during a period when no other process can be examining that buffer. Buffer pin waits can be protracted if another process holds an open cursor which last read data from the buffer in question. Activity: The server process is idle. This is used by system processes waiting for activity in their main processing loop. wait_event will identify the specific wait point. Extension: The server process is waiting for activity in an extension module. This category is useful for modules to track custom waiting points. Client: The server process is waiting for some activity on a socket from user applications, and that the server expects something to happen that is independent from its internal processes. wait_event will identify the specific wait point. IPC: The server process is waiting for some activity from another process in the server. wait_event will identify the specific wait point. Timeout: The server process is waiting for a timeout to expire. wait_event will identify the specific wait point. IO: The server process is waiting for a IO to complete. wait_event will identify the specific wait point.

9. PostgreSQL 9.6 ← 9.5 结构变更

   +wait_event_type+wait_event −waiting 关系说明更新

10. PostgreSQL 9.5 ← 9.4 仅描述更新

    关系说明更新

11. PostgreSQL 9.4 ← 9.3 结构变更

    +backend_xid+backend_xmin 关系说明更新

12. PostgreSQL 9.2 ← 9.1 结构变更

    +pid+state_change+state+query −procpid−current_query 关系说明更新

    2 处描述更新

    • client_hostname 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. 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.
    • query_start Time when the currently active query was started, or if state is not active , when the last query was started Time when the currently active query was started, or if state is not active, when the last query was started

13. PostgreSQL 9.1 ← 9.0 结构变更

    +client_hostname 关系说明更新

字段矩阵

每个字段在 18 个收录版本里的存在情况；方格指向该版的字段表。「有变」指类型、可空、隐式或数组维数与上一版不同。

存在 有变 已移除 不存在

同类关系