27.2. 統計資訊收集器
版本:11
PostgreSQL's statistics collector is a subsystem that supports collection and reporting of information about server activity. Presently, the collector can count accesses to tables and indexes in both disk-block and individual-row terms. It also tracks the total number of rows in each table, and information about vacuum and analyze actions for each table. It can also count calls to user-defined functions and the total time spent in each one.
PostgreSQL also supports reporting dynamic information about exactly what is going on in the system right now, such as the exact command currently being executed by other server processes, and which other connections exist in the system. This facility is independent of the collector process.
27.2.1. Statistics Collection Configuration
Since collection of statistics adds some overhead to query execution, the system can be configured to collect or not collect information. This is controlled by configuration parameters that are normally set in postgresql.conf
. (See Chapter 19 for details about setting configuration parameters.)
The parameter track_activities enables monitoring of the current command being executed by any server process.
The parameter track_counts controls whether statistics are collected about table and index accesses.
The parameter track_functions enables tracking of usage of user-defined functions.
The parameter track_io_timing enables monitoring of block read and write times.
Normally these parameters are set in postgresql.conf
so that they apply to all server processes, but it is possible to turn them on or off in individual sessions using the SET command. (To prevent ordinary users from hiding their activity from the administrator, only superusers are allowed to change these parameters with SET
.)
The statistics collector transmits the collected information to other PostgreSQL processes through temporary files. These files are stored in the directory named by the stats_temp_directory parameter, pg_stat_tmp
by default. For better performance, stats_temp_directory
can be pointed at a RAM-based file system, decreasing physical I/O requirements. When the server shuts down cleanly, a permanent copy of the statistics data is stored in the pg_stat
subdirectory, so that statistics can be retained across server restarts. When recovery is performed at server start (e.g., after immediate shutdown, server crash, and point-in-time recovery), all statistics counters are reset.
27.2.2. Viewing Statistics
Several predefined views, listed in Table 27.1, are available to show the current state of the system. There are also several other views, listed in Table 27.2, available to show the results of statistics collection. Alternatively, one can build custom views using the underlying statistics functions, as discussed in Section 27.2.20.
When using the statistics to monitor collected data, it is important to realize that the information does not update instantaneously. Each individual server process transmits new statistical counts to the collector just before going idle; so a query or transaction still in progress does not affect the displayed totals. Also, the collector itself emits a new report at most once per PGSTAT_STAT_INTERVAL
milliseconds (500 ms unless altered while building the server). So the displayed information lags behind actual activity. However, current-query information collected by track_activities
is always up-to-date.
Another important point is that when a server process is asked to display any of these statistics, it first fetches the most recent report emitted by the collector process and then continues to use this snapshot for all statistical views and functions until the end of its current transaction. So the statistics will show static information as long as you continue the current transaction. Similarly, information about the current queries of all sessions is collected when any such information is first requested within a transaction, and the same information will be displayed throughout the transaction. This is a feature, not a bug, because it allows you to perform several queries on the statistics and correlate the results without worrying that the numbers are changing underneath you. But if you want to see new results with each query, be sure to do the queries outside any transaction block. Alternatively, you can invoke pg_stat_clear_snapshot
(), which will discard the current transaction's statistics snapshot (if any). The next use of statistical information will cause a new snapshot to be fetched.
A transaction can also see its own statistics (as yet untransmitted to the collector) in the views pg_stat_xact_all_tables
, pg_stat_xact_sys_tables
, pg_stat_xact_user_tables
, and pg_stat_xact_user_functions
. These numbers do not act as stated above; instead they update continuously throughout the transaction.
Some of the information in the dynamic statistics views shown in Table 27.1 is security restricted. Ordinary users can only see all the information about their own sessions (sessions belonging to a role that they are a member of). In rows about other sessions, many columns will be null. Note, however, that the existence of a session and its general properties such as its sessions user and database are visible to all users. Superusers and members of the built-in role pg_read_all_stats
(see also Section 21.5) can see all the information about all sessions.
Table 27.1. Dynamic Statistics Views
View Name | Description |
---|---|
| One row per server process, showing information related to the current activity of that process, such as state and current query. See |
| One row per WAL sender process, showing statistics about replication to that sender's connected standby server. See |
| Only one row, showing statistics about the WAL receiver from that receiver's connected server. See |
| At least one row per subscription, showing information about the subscription workers. See |
| One row per connection (regular and replication), showing information about SSL used on this connection. See |
| One row per connection (regular and replication), showing information about GSSAPI authentication and encryption used on this connection. See |
| One row for each backend (including autovacuum worker processes) running |
| One row for each backend running |
| One row for each backend (including autovacuum worker processes) running |
| One row for each backend running |
| One row for each WAL sender process streaming a base backup, showing current progress. See Section 27.4.5. |
Table 27.2. Collected Statistics Views
View Name | Description |
---|---|
| One row only, showing statistics about the WAL archiver process's activity. See |
| One row only, showing statistics about the background writer process's activity. See |
| One row per database, showing database-wide statistics. See |
| One row per database, showing database-wide statistics about query cancels due to conflict with recovery on standby servers. See |
| 目前資料庫中每個資料表為一筆資料,顯示有關對該資料表的存取統計數據。有關詳細資訊,請參閱 pg_stat_all_tables。 |
| 除了僅顯示系統資料表之外,與 pg_stat_all_tables 相同。 |
| 除了僅顯示使用者資料表之外,與 pg_stat_all_tables 相同。 |
| Similar to |
| Same as |
| Same as |
| One row for each index in the current database, showing statistics about accesses to that specific index. See |
| Same as |
| Same as |
| One row for each table in the current database, showing statistics about I/O on that specific table. See |
| Same as |
| Same as |
| One row for each index in the current database, showing statistics about I/O on that specific index. See |
| Same as |
| Same as |
| One row for each sequence in the current database, showing statistics about I/O on that specific sequence. See |
| Same as |
| Same as |
| One row for each tracked function, showing statistics about executions of that function. See |
| Similar to |
| One row per SLRU, showing statistics of operations. See |
The per-index statistics are particularly useful to determine which indexes are being used and how effective they are.
The pg_statio_
views are primarily useful to determine the effectiveness of the buffer cache. When the number of actual disk reads is much smaller than the number of buffer hits, then the cache is satisfying most read requests without invoking a kernel call. However, these statistics do not give the entire story: due to the way in which PostgreSQL handles disk I/O, data that is not in the PostgreSQL buffer cache might still reside in the kernel's I/O cache, and might therefore still be fetched without requiring a physical read. Users interested in obtaining more detailed information on PostgreSQL I/O behavior are advised to use the PostgreSQL statistics collector in combination with operating system utilities that allow insight into the kernel's handling of I/O.
27.2.3. pg_stat_activity
pg_stat_activity
The pg_stat_activity
view will have one row per server process, showing information related to the current activity of that process.
Table 27.3. pg_stat_activity
View
pg_stat_activity
ViewColumn Type Description |
OID of the database this backend is connected to |
Name of the database this backend is connected to |
Process ID of this backend |
Process ID of the parallel group leader, if this process is a parallel query worker. |
OID of the user logged into this backend |
Name of the user logged into this backend |
Name of the application that is connected to this backend |
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. |
Host name of the connected client, as reported by a reverse DNS lookup of |
TCP port number that the client is using for communication with this backend, or |
Time when this process was started. For client backends, this is the time the client connected to the server. |
Time when this process' current transaction was started, or null if no transaction is active. If the current query is the first of its transaction, this column is equal to the |
Time when the currently active query was started, or if |
Time when the |
The type of event for which the backend is waiting, if any; otherwise NULL. See Table 27.4. |
Wait event name if backend is currently waiting, otherwise NULL. See Table 27.5 through Table 27.13. |
Current overall state of this backend. Possible values are:
|
Top-level transaction identifier of this backend, if any. |
The current backend's |
Text of this backend's most recent query. If |
Type of current backend. Possible types are |
Note
The wait_event
and state
columns are independent. If a backend is in the active
state, it may or may not be waiting
on some event. If the state is active
and wait_event
is non-null, it means that a query is being executed, but is being blocked somewhere in the system.
Table 27.4. Wait Event Types
Wait Event Type | Description |
---|---|
| The server process is idle. This event type indicates a process waiting for activity in its main processing loop. |
| The server process is waiting for exclusive access to a data buffer. Buffer pin waits can be protracted if another process holds an open cursor that last read data from the buffer in question. See Table 27.6. |
| The server process is waiting for activity on a socket connected to a user application. Thus, the server expects something to happen that is independent of its internal processes. |
| The server process is waiting for some condition defined by an extension module. See Table 27.8. |
| The server process is waiting for an I/O operation to complete. |
| The server process is waiting for some interaction with another server process. |
| The server process 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. |
| The server process is waiting for a lightweight lock. Most such locks protect a particular data structure in shared memory. |
| The server process is waiting for a timeout to expire. |
Table 27.5. Wait Events of Type Activity
Activity
| Description |
| Waiting in main loop of archiver process. |
| Waiting in main loop of autovacuum launcher process. |
| Waiting in background writer process, hibernating. |
| Waiting in main loop of background writer process. |
| Waiting in main loop of checkpointer process. |
| Waiting in main loop of logical replication apply process. |
| Waiting in main loop of logical replication launcher process. |
| Waiting in main loop of statistics collector process. |
| Waiting in main loop of startup process for WAL to arrive, during streaming recovery. |
| Waiting in main loop of syslogger process. |
| Waiting in main loop of WAL receiver process. |
| Waiting in main loop of WAL sender process. |
| Waiting in main loop of WAL writer process. |
Table 27.6. Wait Events of Type BufferPin
BufferPin
| Description |
| Waiting to acquire an exclusive pin on a buffer. |
Table 27.7. Wait Events of Type Client
Client
| Description |
| Waiting to read data from the client. |
| Waiting to write data to the client. |
| Waiting to read data from the client while establishing a GSSAPI session. |
| Waiting in WAL receiver to establish connection to remote server. |
| Waiting in WAL receiver to receive data from remote server. |
| Waiting for SSL while attempting connection. |
| Waiting for startup process to send initial data for streaming replication. |
| Waiting for WAL to be flushed in WAL sender process. |
| Waiting for any activity when processing replies from WAL receiver in WAL sender process. |
Table 27.8. Wait Events of Type Extension
Extension
| Description |
| Waiting in an extension. |
Table 27.9. Wait Events of Type IO
IO
| Description |
| Waiting for a read from a buffered file. |
| Waiting for a write to a buffered file. |
| Waiting for a read from the |
| Waiting for the |
| Waiting for an update to the |
| Waiting for a write to the |
| Waiting for a write to update the |
| Waiting for a read during a file copy operation. |
| Waiting for a write during a file copy operation. |
| Waiting to fill a dynamic shared memory backing file with zeroes. |
| Waiting for a relation data file to be extended. |
| Waiting for a relation data file to reach durable storage. |
| Waiting for an immediate synchronization of a relation data file to durable storage. |
| Waiting for an asynchronous prefetch from a relation data file. |
| Waiting for a read from a relation data file. |
| Waiting for changes to a relation data file to reach durable storage. |
| Waiting for a relation data file to be truncated. |
| Waiting for a write to a relation data file. |
| Waiting for a read while adding a line to the data directory lock file. |
| Waiting for data to reach durable storage while adding a line to the data directory lock file. |
| Waiting for a write while adding a line to the data directory lock file. |
| Waiting to read while creating the data directory lock file. |
| Waiting for data to reach durable storage while creating the data directory lock file. |
| Waiting for a write while creating the data directory lock file. |
| Waiting for a read during recheck of the data directory lock file. |
| Waiting for logical rewrite mappings to reach durable storage during a checkpoint. |
| Waiting for mapping data to reach durable storage during a logical rewrite. |
| Waiting for a write of mapping data during a logical rewrite. |
| Waiting for logical rewrite mappings to reach durable storage. |
| Waiting for truncate of mapping data during a logical rewrite. |
| Waiting for a write of logical rewrite mappings. |
| Waiting for a read of the relation map file. |
| Waiting for the relation map file to reach durable storage. |
| Waiting for a write to the relation map file. |
| Waiting for a read during reorder buffer management. |
| Waiting for a write during reorder buffer management. |
| Waiting for a read of a logical mapping during reorder buffer management. |
| Waiting for a read from a replication slot control file. |
| Waiting for a replication slot control file to reach durable storage while restoring it to memory. |
| Waiting for a replication slot control file to reach durable storage. |
| Waiting for a write to a replication slot control file. |
| Waiting for SLRU data to reach durable storage during a checkpoint or database shutdown. |
| Waiting for a read of an SLRU page. |
| Waiting for SLRU data to reach durable storage following a page write. |
| Waiting for a write of an SLRU page. |
| Waiting for a read of a serialized historical catalog snapshot. |
| Waiting for a serialized historical catalog snapshot to reach durable storage. |
| Waiting for a write of a serialized historical catalog snapshot. |
| Waiting for a timeline history file received via streaming replication to reach durable storage. |
| Waiting for a write of a timeline history file received via streaming replication. |
| Waiting for a read of a timeline history file. |
| Waiting for a newly created timeline history file to reach durable storage. |
| Waiting for a write of a newly created timeline history file. |
| Waiting for a read of a two phase state file. |
| Waiting for a two phase state file to reach durable storage. |
| Waiting for a write of a two phase state file. |
| Waiting for WAL to reach durable storage during bootstrapping. |
| Waiting for a write of a WAL page during bootstrapping. |
| Waiting for a read when creating a new WAL segment by copying an existing one. |
| Waiting for a new WAL segment created by copying an existing one to reach durable storage. |
| Waiting for a write when creating a new WAL segment by copying an existing one. |
| Waiting for a newly initialized WAL file to reach durable storage. |
| Waiting for a write while initializing a new WAL file. |
| Waiting for a read from a WAL file. |
| Waiting for a read from a timeline history file during a walsender timeline command. |
| Waiting for a WAL file to reach durable storage. |
| Waiting for data to reach durable storage while assigning a new WAL sync method. |
| Waiting for a write to a WAL file. |
Table 27.10. Wait Events of Type IPC
IPC
| Description |
| Waiting for WAL files required for a backup to be successfully archived. |
| Waiting for background worker to shut down. |
| Waiting for background worker to start up. |
| Waiting for the page number needed to continue a parallel B-tree scan to become available. |
| Waiting for a checkpoint to complete. |
| Waiting for a checkpoint to start. |
| Waiting for activity from a child process while executing a |
| Waiting for an elected Parallel Hash participant to allocate a hash table. |
| Waiting to elect a Parallel Hash participant to allocate a hash table. |
| Waiting for other Parallel Hash participants to finish loading a hash table. |
| Waiting for an elected Parallel Hash participant to allocate the initial hash table. |
| Waiting to elect a Parallel Hash participant to allocate the initial hash table. |
| Waiting for other Parallel Hash participants to finish hashing the inner relation. |
| Waiting for other Parallel Hash participants to finish partitioning the outer relation. |
| Waiting for an elected Parallel Hash participant to allocate more batches. |
| Waiting to elect a Parallel Hash participant to decide on future batch growth. |
| Waiting to elect a Parallel Hash participant to allocate more batches. |
| Waiting for an elected Parallel Hash participant to decide on future batch growth. |
| Waiting for other Parallel Hash participants to finish repartitioning. |
| Waiting for an elected Parallel Hash participant to finish allocating more buckets. |
| Waiting to elect a Parallel Hash participant to allocate more buckets. |
| Waiting for other Parallel Hash participants to finish inserting tuples into new buckets. |
| Waiting for a logical replication remote server to send data for initial table synchronization. |
| Waiting for a logical replication remote server to change state. |
| Waiting for another process to be attached to a shared message queue. |
| Waiting to write a protocol message to a shared message queue. |
| Waiting to receive bytes from a shared message queue. |
| Waiting to send bytes to a shared message queue. |
| Waiting for parallel bitmap scan to become initialized. |
| Waiting for parallel |
| Waiting for parallel workers to finish computing. |
| Waiting for the group leader to clear the transaction ID at end of a parallel operation. |
| Waiting for a barrier event to be processed by all backends. |
| Waiting for standby promotion. |
| Waiting for recovery conflict resolution for a vacuum cleanup. |
| Waiting for recovery conflict resolution for dropping a tablespace. |
| Waiting for recovery to be resumed. |
| Waiting for a replication origin to become inactive so it can be dropped. |
| Waiting for a replication slot to become inactive so it can be dropped. |
| Waiting to obtain a valid snapshot for a |
| Waiting for confirmation from a remote server during synchronous replication. |
| Waiting for the group leader to update transaction status at end of a parallel operation. |
Table 27.11. Wait Events of Type Lock
Lock
| Description |
| Waiting to acquire an advisory user lock. |
| Waiting to extend a relation. |
| Waiting to update |
| Waiting to acquire a lock on a non-relation database object. |
| Waiting to acquire a lock on a page of a relation. |
| Waiting to acquire a lock on a relation. |
| Waiting to acquire a speculative insertion lock. |
| Waiting for a transaction to finish. |
| Waiting to acquire a lock on a tuple. |
| Waiting to acquire a user lock. |
| Waiting to acquire a virtual transaction ID lock. |
Table 27.12. Wait Events of Type LWLock
LWLock
| Description |
| Waiting to manage an extension's space allocation in shared memory. |
| Waiting to update the |
| Waiting to read or update the current state of autovacuum workers. |
| Waiting to ensure that a table selected for autovacuum still needs vacuuming. |
| Waiting to read or update background worker state. |
| Waiting to read or update vacuum-related information for a B-tree index. |
| Waiting to access a data page in memory. |
| Waiting for I/O on a data page. |
| Waiting to associate a data block with a buffer in the buffer pool. |
| Waiting to begin a checkpoint. |
| Waiting to manage fsync requests. |
| Waiting to read or update the last value set for a transaction commit timestamp. |
| Waiting for I/O on a commit timestamp SLRU buffer. |
| Waiting to access the commit timestamp SLRU cache. |
| Waiting to read or update the |
| Waiting to read or update dynamic shared memory allocation information. |
| Waiting to read or update a process' fast-path lock information. |
| Waiting to read or update information about “heavyweight” locks. |
| Waiting to read or update the state of logical replication workers. |
| Waiting to read or update shared multixact state. |
| Waiting for I/O on a multixact member SLRU buffer. |
| Waiting to access the multixact member SLRU cache. |
| Waiting for I/O on a multixact offset SLRU buffer. |
| Waiting to access the multixact offset SLRU cache. |
| Waiting to read or truncate multixact information. |
| Waiting for I/O on a |
| Waiting to read or update |
| Waiting to update limit on |
| Waiting to access the |
| Waiting to allocate a new OID. |
| Waiting to read or update old snapshot control information. |
| Waiting to choose the next subplan during Parallel Append plan execution. |
| Waiting to synchronize workers during Parallel Hash Join plan execution. |
| Waiting for parallel query dynamic shared memory allocation. |
| Waiting for parallel query dynamic shared memory allocation. |
| Waiting to access a parallel query's information about composite types. |
| Waiting to access a parallel query's information about type modifiers that identify anonymous record types. |
| Waiting to access the list of predicate locks held by the current serializable transaction during a parallel query. |
| Waiting to access predicate lock information used by serializable transactions. |
| Waiting to access the shared per-process data structures (typically, to get a snapshot or report a session's transaction ID). |
| Waiting to read or update a |
| Waiting to read or update a |
| Waiting to create, drop or use a replication origin. |
| Waiting to read or update the progress of one replication origin. |
| Waiting to allocate or free a replication slot. |
| Waiting to read or update replication slot state. |
| Waiting for I/O on a replication slot. |
| Waiting for I/O on a serializable transaction conflict SLRU buffer. |
| Waiting to access the list of finished serializable transactions. |
| Waiting to access the list of predicate locks held by serializable transactions. |
| Waiting to read or update information about serializable transactions. |
| Waiting to access the serializable transaction conflict SLRU cache. |
| Waiting to access a shared TID bitmap during a parallel bitmap index scan. |
| Waiting to access a shared tuple store during parallel query. |
| Waiting to find or allocate space in shared memory. |
| Waiting to retrieve messages from the shared catalog invalidation queue. |
| Waiting to add a message to the shared catalog invalidation queue. |
| Waiting for I/O on a sub-transaction SLRU buffer. |
| Waiting to access the sub-transaction SLRU cache. |
| Waiting to read or update information about the state of synchronous replication. |
| Waiting to select the starting location of a synchronized table scan. |
| Waiting to create or drop a tablespace. |
| Waiting to read or update the state of prepared transactions. |
| Waiting to replace a page in WAL buffers. |
| Waiting to insert WAL data into a memory buffer. |
| Waiting for WAL buffers to be written to disk. |
| Waiting to update limits on transaction id and multixact consumption. |
| Waiting for I/O on a transaction status SLRU buffer. |
| Waiting to access the transaction status SLRU cache. |
| Waiting to execute |
| Waiting to allocate a new transaction ID. |
Note
Extensions can add LWLock
types to the list shown in Table 27.12. In some cases, the name assigned by an extension will not be available in all server processes; so an LWLock
wait event might be reported as just “extension
” rather than the extension-assigned name.
Table 27.13. Wait Events of Type Timeout
Timeout
| Description |
| Waiting during base backup when throttling activity. |
| Waiting due to a call to |
| Waiting to apply WAL during recovery because of a delay setting. |
| Waiting during recovery when WAL data is not available from any source ( |
| Waiting in a cost-based vacuum delay point. |
Here is an example of how wait events can be viewed:
27.2.4. pg_stat_replication
pg_stat_replication
pg_stat_replication 檢視表中的每一筆資料表示每個 WAL 發送者的執行程序,顯示有關複製到該發送者的備用伺服器統計資訊。僅列出直接連接的備用資料庫,不會包含其下游備用伺服器的資訊。
Table 27.14. pg_stat_replication
View
pg_stat_replication
ViewColumn Type Description |
Process ID of a WAL sender process |
OID of the user logged into this WAL sender process |
Name of the user logged into this WAL sender process |
Name of the application that is connected to this WAL sender |
IP address of the client connected to this WAL sender. If this field is null, it indicates that the client is connected via a Unix socket on the server machine. |
Host name of the connected client, as reported by a reverse DNS lookup of |
TCP port number that the client is using for communication with this WAL sender, or |
Time when this process was started, i.e., when the client connected to this WAL sender |
This standby's |
Current WAL sender state. Possible values are:
|
Last write-ahead log location sent on this connection |
Last write-ahead log location written to disk by this standby server |
Last write-ahead log location flushed to disk by this standby server |
Last write-ahead log location replayed into the database on this standby server |
Time elapsed between flushing recent WAL locally and receiving notification that this standby server has written it (but not yet flushed it or applied it). This can be used to gauge the delay that |
Time elapsed between flushing recent WAL locally and receiving notification that this standby server has written and flushed it (but not yet applied it). This can be used to gauge the delay that |
Time elapsed between flushing recent WAL locally and receiving notification that this standby server has written, flushed and applied it. This can be used to gauge the delay that |
Priority of this standby server for being chosen as the synchronous standby in a priority-based synchronous replication. This has no effect in a quorum-based synchronous replication. |
Synchronous state of this standby server. Possible values are:
|
最後從備用伺服器收到回覆訊息的發送時間 |
The lag times reported in the pg_stat_replication
view are measurements of the time taken for recent WAL to be written, flushed and replayed and for the sender to know about it. These times represent the commit delay that was (or would have been) introduced by each synchronous commit level, if the remote server was configured as a synchronous standby. For an asynchronous standby, the replay_lag
column approximates the delay before recent transactions became visible to queries. If the standby server has entirely caught up with the sending server and there is no more WAL activity, the most recently measured lag times will continue to be displayed for a short time and then show NULL.
Lag times work automatically for physical replication. Logical decoding plugins may optionally emit tracking messages; if they do not, the tracking mechanism will simply display NULL lag.
Note
The reported lag times are not predictions of how long it will take for the standby to catch up with the sending server assuming the current rate of replay. Such a system would show similar times while new WAL is being generated, but would differ when the sender becomes idle. In particular, when the standby has caught up completely, pg_stat_replication
shows the time taken to write, flush and replay the most recent reported WAL location rather than zero as some users might expect. This is consistent with the goal of measuring synchronous commit and transaction visibility delays for recent write transactions. To reduce confusion for users expecting a different model of lag, the lag columns revert to NULL after a short time on a fully replayed idle system. Monitoring systems should choose whether to represent this as missing data, zero or continue to display the last known value.
27.2.5. pg_stat_wal_receiver
pg_stat_wal_receiver
The pg_stat_wal_receiver
view will contain only one row, showing statistics about the WAL receiver from that receiver's connected server.
Table 27.15. pg_stat_wal_receiver
View
pg_stat_wal_receiver
ViewColumn Type Description |
Process ID of the WAL receiver process |
Activity status of the WAL receiver process |
First write-ahead log location used when WAL receiver is started |
First timeline number used when WAL receiver is started |
Last write-ahead log location already received and written to disk, but not flushed. This should not be used for data integrity checks. |
Last write-ahead log location already received and flushed to disk, the initial value of this field being the first log location used when WAL receiver is started |
Timeline number of last write-ahead log location received and flushed to disk, the initial value of this field being the timeline number of the first log location used when WAL receiver is started |
Send time of last message received from origin WAL sender |
Receipt time of last message received from origin WAL sender |
Last write-ahead log location reported to origin WAL sender |
Time of last write-ahead log location reported to origin WAL sender |
Replication slot name used by this WAL receiver |