27.2. The Cumulative Statistics System
The Cumulative Statistics System
PostgreSQL's cumulative statistics system supports collection and reporting of information about server activity. Presently, accesses to tables and indexes in both disk-block and individual-row terms are counted. The total number of rows in each table, and information about vacuum and analyze actions for each table are also counted. If enabled, calls to user-defined functions and the total time spent in each one are counted as well.
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 cumulative statistics system.
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 Server Configuration for details about setting configuration parameters.)
The parameter [track_activities (boolean)
track_activities configuration parameter](braised:ref/runtime-config-statistics#track-activities-boolean-track-activities-configuration-parameter) enables monitoring of the current command being executed by any server process.
The parameter [track_cost_delay_timing (boolean)
track_cost_delay_timing configuration parameter](braised:ref/runtime-config-statistics#track-cost-delay-timing-boolean-track-cost-delay-timing-configuration-parameter) enables monitoring of cost-based vacuum delay.
The parameter [track_counts (boolean)
track_counts configuration parameter](braised:ref/runtime-config-statistics#track-counts-boolean-track-counts-configuration-parameter) controls whether cumulative statistics are collected about table and index accesses.
The parameter [track_functions (enum)
track_functions configuration parameter](braised:ref/runtime-config-statistics#track-functions-enum-track-functions-configuration-parameter) enables tracking of usage of user-defined functions.
The parameter [track_io_timing (boolean)
track_io_timing configuration parameter](braised:ref/runtime-config-statistics#track-io-timing-boolean-track-io-timing-configuration-parameter) enables monitoring of block read, write, extend, and fsync times.
The parameter [track_wal_io_timing (boolean)
track_wal_io_timing configuration parameter](braised:ref/runtime-config-statistics#track-wal-io-timing-boolean-track-wal-io-timing-configuration-parameter) enables monitoring of WAL read, write and fsync 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.)
Cumulative statistics are collected in shared memory.
Every PostgreSQL process collects statistics locally, then updates the shared data at appropriate intervals.
When a server, including a physical replica, 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.
In contrast, when starting from an unclean shutdown (e.g., after an immediate shutdown, a server crash, starting from a base backup, and point-in-time recovery), all statistics counters are reset.
Viewing Statistics
Several predefined views, listed in Dynamic Statistics Views, are available to show the current state of the system. There are also several other views, listed in Collected Statistics Views, available to show the accumulated statistics. Alternatively, one can build custom views using the underlying cumulative statistics functions, as discussed in Statistics Functions.
When using the cumulative statistics views and functions to monitor collected data, it is important to realize that the information does not update instantaneously.
Each individual server process flushes out accumulated statistics to shared memory just before going idle, but not more frequently than once per PGSTAT_MIN_INTERVAL milliseconds (1 second unless altered while building the server); so a query or transaction still in progress does not affect the displayed totals and 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 the accumulated statistics, accessed values are cached until the end of its current transaction in the default configuration.
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.
When analyzing statistics interactively, or with expensive queries, the time delta between accesses to individual statistics can lead to significant skew in the cached statistics.
To minimize skew, stats_fetch_consistency can be set to snapshot, at the price of increased memory usage for caching not-needed statistics data.
Conversely, if it's known that statistics are only accessed once, caching accessed statistics is unnecessary and can be avoided by setting stats_fetch_consistency to none.
You can invoke pg_stat_clear_snapshot() to discard the current transaction's statistics snapshot or cached values (if any).
The next use of statistical information will (when in snapshot mode) cause a new snapshot to be built or (when in cache mode) accessed statistics to be cached.
A transaction can also see its own statistics (not yet flushed out to the shared memory statistics) 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 Dynamic Statistics Views 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 roles with privileges of built-in role pg_read_all_stats can see all the information about all sessions.
View Name |
Description |
|---|---|
pg_stat_activity |
One row per server process, showing information related to the current activity of that process, such as state and current query. See pg_stat_activity for details. |
pg_stat_replication |
One row per WAL sender process, showing statistics about replication to that sender's connected standby server. See pg_stat_replication for details. |
pg_stat_wal_receiver |
Only one row, showing statistics about the WAL receiver from that receiver's connected server. See pg_stat_wal_receiver for details. |
pg_stat_recovery_prefetch |
Only one row, showing statistics about blocks prefetched during recovery. See pg_stat_recovery_prefetch for details. |
pg_stat_subscription |
At least one row per subscription, showing information about the subscription workers. See pg_stat_subscription for details. |
pg_stat_ssl |
One row per connection (regular and replication), showing information about SSL used on this connection. See pg_stat_ssl for details. |
pg_stat_gssapi |
One row per connection (regular and replication), showing information about GSSAPI authentication and encryption used on this connection. See pg_stat_gssapi for details. |
pg_stat_progress_analyze |
One row for each backend (including autovacuum worker processes) running |
pg_stat_progress_create_index |
One row for each backend running |
pg_stat_progress_vacuum |
One row for each backend (including autovacuum worker processes) running |
pg_stat_progress_cluster |
One row for each backend running |
pg_stat_progress_basebackup |
One row for each WAL sender process streaming a base backup, showing current progress. See Base Backup Progress Reporting. |
pg_stat_progress_copy |
One row for each backend running |
: Dynamic Statistics Views
View Name |
Description |
|---|---|
pg_stat_archiver |
One row only, showing statistics about the WAL archiver process's activity. See pg_stat_archiver for details. |
pg_stat_bgwriter |
One row only, showing statistics about the background writer process's activity. See pg_stat_bgwriter for details. |
pg_stat_checkpointer |
One row only, showing statistics about the checkpointer process's activity. See pg_stat_checkpointer for details. |
pg_stat_database |
One row per database, showing database-wide statistics. See pg_stat_database for details. |
pg_stat_database_conflicts |
One row per database, showing database-wide statistics about query cancels due to conflict with recovery on standby servers. See pg_stat_database_conflicts for details. |
pg_stat_io |
One row for each combination of backend type, context, and target object containing cluster-wide I/O statistics. See pg_stat_io for details. |
pg_stat_replication_slots |
One row per replication slot, showing statistics about the replication slot's usage. See pg_stat_replication_slots for details. |
pg_stat_slru |
One row per SLRU, showing statistics of operations. See pg_stat_slru for details. |
pg_stat_subscription_stats |
One row per subscription, showing statistics about errors and conflicts. See pg_stat_subscription_stats for details. |
pg_stat_wal |
One row only, showing statistics about WAL activity. See pg_stat_wal for details. |
pg_stat_all_tables |
One row for each table in the current database, showing statistics about accesses to that specific table. See pg_stat_all_tables for details. |
pg_stat_sys_tables |
Same as pg_stat_all_tables, except that only system tables are shown. |
pg_stat_user_tables |
Same as pg_stat_all_tables, except that only user tables are shown. |
pg_stat_xact_all_tables |
Similar to pg_stat_all_tables, but counts actions taken so far within the current transaction (which are not yet included in pg_stat_all_tables and related views). The columns for numbers of live and dead rows and vacuum and analyze actions are not present in this view. |
pg_stat_xact_sys_tables |
Same as pg_stat_xact_all_tables, except that only system tables are shown. |
pg_stat_xact_user_tables |
Same as pg_stat_xact_all_tables, except that only user tables are shown. |
pg_stat_all_indexes |
One row for each index in the current database, showing statistics about accesses to that specific index. See pg_stat_all_indexes for details. |
pg_stat_sys_indexes |
Same as pg_stat_all_indexes, except that only indexes on system tables are shown. |
pg_stat_user_indexes |
Same as pg_stat_all_indexes, except that only indexes on user tables are shown. |
pg_stat_user_functions |
One row for each tracked function, showing statistics about executions of that function. See pg_stat_user_functions for details. |
pg_stat_xact_user_functions |
Similar to pg_stat_user_functions, but counts only calls during the current transaction (which are not yet included in pg_stat_user_functions). |
pg_statio_all_tables |
One row for each table in the current database, showing statistics about I/O on that specific table. See pg_statio_all_tables for details. |
pg_statio_sys_tables |
Same as pg_statio_all_tables, except that only system tables are shown. |
pg_statio_user_tables |
Same as pg_statio_all_tables, except that only user tables are shown. |
pg_statio_all_indexes |
One row for each index in the current database, showing statistics about I/O on that specific index. See pg_statio_all_indexes for details. |
pg_statio_sys_indexes |
Same as pg_statio_all_indexes, except that only indexes on system tables are shown. |
pg_statio_user_indexes |
Same as pg_statio_all_indexes, except that only indexes on user tables are shown. |
pg_statio_all_sequences |
One row for each sequence in the current database, showing statistics about I/O on that specific sequence. See pg_statio_all_sequences for details. |
pg_statio_sys_sequences |
Same as pg_statio_all_sequences, except that only system sequences are shown. (Presently, no system sequences are defined, so this view is always empty.) |
pg_statio_user_sequences |
Same as pg_statio_all_sequences, except that only user sequences are shown. |
: Collected Statistics Views
The per-index statistics are particularly useful to determine which indexes are being used and how effective they are.
The pg_stat_io and pg_statio_ set of views are useful for determining the effectiveness of the buffer cache. They can be used to calculate a cache hit ratio. Note that while PostgreSQL's I/O statistics capture most instances in which the kernel was invoked in order to perform I/O, they do not differentiate between data which had to be fetched from disk and that which already resided in the kernel page cache. Users are advised to use the PostgreSQL statistics views in combination with operating system utilities for a more complete picture of their database's I/O performance.
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.
Column Type Description |
|---|
datid OID of the database this backend is connected to |
datname Name of the database this backend is connected to |
pid Process ID of this backend |
leader_pid 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. |
usesysid OID of the user logged into this backend |
usename Name of the user logged into this backend |
application_name Name of the application that is connected to this backend |
client_addr 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 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 (boolean)
|
client_port TCP port number that the client is using for communication with this backend, or |
backend_start Time when this process was started. For client backends, this is the time the client connected to the server. |
xact_start 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 query_start column. |
query_start Time when the currently active query was started, or if state is not |
state_change Time when the state was last changed |
wait_event_type The type of event for which the backend is waiting, if any; otherwise NULL. See Wait Event Types. |
wait_event Wait event name if backend is currently waiting, otherwise NULL. See Wait Events of Type through Wait Events of Type . |
state Current overall state of this backend. Possible values are:
|
backend_xid Top-level transaction identifier of this backend, if any; see Transactions and Identifiers. |
backend_xmin The current backend's |
query_id Identifier of this backend's most recent query. If state is
|
query Text of this backend's most recent query. If state is
|
backend_type Type of current backend. Possible types are |
: pg_stat_activity View
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. To keep the reporting overhead low, the system does not attempt to synchronize different aspects of activity data for a backend. As a result, ephemeral discrepancies may exist between the view's columns.
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 Wait Event Types. |
|
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 Wait Events of Type . |
|
The server process is waiting for an injection point to reach an outcome defined in a test. See Injection Points for more details. This type has no predefined wait points. |
|
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. |
: Wait Event Types
|
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 for checkpointer process to be terminated. |
|
Waiting in main loop of IO Worker process. |
|
Waiting in main loop of logical replication apply process. |
|
Waiting in main loop of logical replication launcher process. |
|
Waiting in main loop of logical replication parallel apply process. |
|
Waiting in main loop of startup process for WAL to arrive, during streaming recovery. |
|
Waiting in main loop of slot synchronization. |
|
Waiting for slot sync worker to shut down. |
|
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 WAL summarizer for more WAL to be generated. |
|
Waiting in main loop of WAL writer process. |
: Wait Events of Type Activity
|
Description |
|---|---|
|
Waiting to acquire an exclusive pin on a buffer. Buffer pin waits can be protracted if another process holds an open cursor that last read data from the buffer in question. |
|
Waiting to acquire a exclusive lock on a buffer. |
|
Waiting to acquire a shared lock on a buffer. |
|
Waiting to acquire a share exclusive lock on a buffer. |
: Wait Events of Type Buffer
|
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 WAL to be received and flushed by the physical standby. |
|
Waiting for WAL flush to reach a target LSN on a primary or standby. |
|
Waiting for WAL replay to reach a target LSN on a standby. |
|
Waiting for WAL write to reach a target LSN on a standby. |
|
Waiting for WAL to be flushed in WAL sender process. |
|
Waiting for any activity when processing replies from WAL receiver in WAL sender process. |
: Wait Events of Type Client
|
Description |
|---|---|
|
Waiting in an extension. |
: Wait Events of Type Extension
|
Description |
|---|---|
|
Waiting for another process to complete IO. |
|
Waiting for IO execution via io_uring. |
|
Waiting for IO submission via io_uring. |
|
Waiting for base backup to read from a file. |
|
Waiting for data written by a base backup to reach durable storage. |
|
Waiting for base backup to write to a file. |
|
Waiting for a read from a buffered file. |
|
Waiting for a buffered file to be truncated. |
|
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 file copy operation. |
|
Waiting for a read during a file copy operation. |
|
Waiting for a write during a file copy operation. |
|
Waiting to read data from a pipe, a file or a program during COPY FROM. |
|
Waiting to write data to a pipe, a file or a program during COPY TO. |
|
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 dynamic shared memory segment to be allocated. |
|
Waiting to fill a dynamic shared memory backing file with zeroes. |
|
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 durable replacement of a relation map file. |
|
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 the version file to reach durable storage while creating a database. |
|
Waiting for the version file to be written while creating a database. |
|
Waiting for a read from a timeline history file during a walsender timeline command. |
|
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 WAL summary file. |
|
Waiting for a write to a WAL summary file. |
|
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. |
: Wait Events of Type Io
|
Description |
|---|---|
|
Waiting for subplan nodes of an |
|
Waiting for [archive_cleanup_command (string)
|
|
Waiting for [archive_command (string)
|
|
Waiting for the termination of another backend. |
|
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 buffer I/O to complete. |
|
Waiting for a backend that blocks a checkpoint from completing. |
|
Waiting for a backend that blocks a checkpoint from starting. |
|
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 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 an elected Parallel Hash participant to allocate more batches. |
|
Waiting for other Parallel Hash participants to finish repartitioning. |
|
Waiting to elect a Parallel Hash participant to allocate more buckets. |
|
Waiting for an elected Parallel Hash participant to finish allocating more buckets. |
|
Waiting for other Parallel Hash participants to finish inserting tuples into new buckets. |
|
Waiting for a logical replication leader apply process to send data to a parallel apply process. |
|
Waiting for a logical replication parallel apply process to change state. |
|
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 a multixact creation to complete. |
|
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 transaction end. |
|
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_end_command (string)
|
|
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 for [restore_command (string)
|
|
Waiting to obtain a valid snapshot for a |
|
Waiting for confirmation from a remote server during synchronous replication. |
|
Waiting for the WAL receiver to exit. |
|
Waiting for startup process to send initial data for streaming replication. |
|
Waiting for a new WAL summary to be generated. |
|
Waiting for the group leader to update transaction status at transaction end. |
: Wait Events of Type Ipc
|
Description |
|---|---|
|
Waiting to acquire an advisory user lock. |
|
Waiting to acquire a lock on a remote transaction being applied by a logical replication subscriber. |
|
Waiting to extend a relation. |
|
Waiting to update pg_database.datfrozenxid and pg_database.datminmxid. |
|
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; see Transactions and Identifiers. |
: Wait Events of Type Lock
|
Description |
|---|---|
|
Waiting to manage an extension's space allocation in shared memory. |
|
Waiting for another process to complete IO via io_uring. |
|
Waiting to access AIO worker submission queue. |
|
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 associate a data block with a buffer in the buffer pool. |
|
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 the dynamic shared memory registry. |
|
Waiting to access dynamic shared memory registry's dynamic shared memory allocator. |
|
Waiting to access dynamic shared memory registry's shared hash table. |
|
Waiting to read or update dynamic shared memory allocation information. |
|
Waiting to read or update information related to injection points. |
|
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 logical decoding status information. |
|
Waiting to access logical replication launcher's dynamic shared memory allocator. |
|
Waiting to access logical replication launcher's shared hash table. |
|
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 access the |
|
Waiting to read or update |
|
Waiting to update limit on |
|
Waiting to access the |
|
Waiting to allocate a new OID. |
|
Waiting to choose the next subplan during Parallel Append plan execution. |
|
Waiting to synchronize workers during Parallel B-tree scan plan execution. |
|
Waiting to synchronize workers during Parallel Hash Join plan execution. |
|
Waiting for parallel query dynamic shared memory allocation. |
|
Waiting for parallel vacuum 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 for shared memory stats data access. |
|
Waiting for stats dynamic shared memory allocator access. |
|
Waiting for stats shared memory hash table access. |
|
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 read or update shared |
|
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 read or update custom wait events information. |
|
Waiting to read or update shared Wait-for-LSN state. |
|
Waiting to replace a page in WAL buffers. |
|
Waiting to insert WAL data into a memory buffer. |
|
Waiting to read or update WAL summarization state. |
|
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. |
: Wait Events of Type Lwlock
|
Description |
|---|---|
|
Waiting during base backup when throttling activity. |
|
Waiting between writes while performing a checkpoint. |
|
Waiting for commit delay before WAL flush. |
|
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 while sending synchronization requests to the checkpointer, because the request queue is full. |
|
Waiting while acquiring a contended spinlock. |
|
Waiting in a cost-based vacuum delay point. |
|
Waiting to acquire an exclusive lock to truncate off any empty pages at the end of a table vacuumed. |
|
Waiting after a WAL summarizer error. |
: Wait Events of Type Timeout
Here are examples of how wait events can be viewed:
SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event is NOT NULL;
pid | wait_event_type | wait_event
------+-----------------+------------
2540 | Lock | relation
6644 | LWLock | ProcArray
(2 rows)
SELECT a.pid, a.wait_event, w.description
FROM pg_stat_activity a JOIN
pg_wait_events w ON (a.wait_event_type = w.type AND
a.wait_event = w.name)
WHERE a.wait_event is NOT NULL and a.state = 'active';
-[ RECORD 1 ]------------------------------------------------------------------
pid | 686674
wait_event | WALInitSync
description | Waiting for a newly initialized WAL file to reach durable storage
Extensions can add Extension, InjectionPoint, and LWLock events to the lists shown in Wait Events of Type and Wait Events of Type . In some cases, the name of an LWLock assigned by an extension will not be available in all server processes. It might be reported as just "extension" rather than the extension-assigned name.
pg_stat_replication
The pg_stat_replication view will contain one row per WAL sender process, showing statistics about replication to that sender's connected standby server. Only directly connected standbys are listed; no information is available about downstream standby servers.
Column Type Description |
|---|
pid Process ID of a WAL sender process |
usesysid OID of the user logged into this WAL sender process |
usename Name of the user logged into this WAL sender process |
application_name Name of the application that is connected to this WAL sender |
client_addr 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. |
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 (boolean)
|
client_port TCP port number that the client is using for communication with this WAL sender, or |
backend_start Time when this process was started, i.e., when the client connected to this WAL sender |
backend_xmin This standby's
|
state Current WAL sender state. Possible values are:
|
sent_lsn Last write-ahead log location sent on this connection |
write_lsn Last write-ahead log location written to disk by this standby server |
flush_lsn Last write-ahead log location flushed to disk by this standby server |
replay_lsn Last write-ahead log location replayed into the database on this standby server |
write_lag 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 |
flush_lag 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 |
replay_lag 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 |
sync_priority 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. |
sync_state Synchronous state of this standby server. Possible values are:
|
reply_time Send time of last reply message received from standby server |
: pg_stat_replication View
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.
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.
pg_stat_replication_slots
The pg_stat_replication_slots view will contain one row per logical replication slot, showing statistics about its usage.
Column Type Description |
|---|
slot_name A unique, cluster-wide identifier for the replication slot |
spill_txns Number of transactions spilled to disk once the memory used by logical decoding to decode changes from WAL has exceeded |
spill_count Number of times transactions were spilled to disk while decoding changes from WAL for this slot. This counter is incremented each time a transaction is spilled, and the same transaction may be spilled multiple times. |
spill_bytes Amount of decoded transaction data spilled to disk while performing decoding of changes from WAL for this slot. This and other spill counters can be used to gauge the I/O which occurred during logical decoding and allow tuning |
stream_txns Number of in-progress transactions streamed to the decoding output plugin after the memory used by logical decoding to decode changes from WAL for this slot has exceeded |
stream_count Number of times in-progress transactions were streamed to the decoding output plugin while decoding changes from WAL for this slot. This counter is incremented each time a transaction is streamed, and the same transaction may be streamed multiple times. |
stream_bytes Amount of transaction data decoded for streaming in-progress transactions to the decoding output plugin while decoding changes from WAL for this slot. This and other streaming counters for this slot can be used to tune |
total_txns Number of decoded transactions sent to the decoding output plugin for this slot. This counts top-level transactions only, and is not incremented for subtransactions. Note that this includes the transactions that are streamed and/or spilled. |
total_bytes Amount of transaction data decoded for sending transactions to the decoding output plugin while decoding changes from WAL for this slot. Note that this includes data that is streamed and/or spilled. |
stats_reset Time at which these statistics were last reset |
: pg_stat_replication_slots View
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.
Column Type Description |
|---|
pid Process ID of the WAL receiver process |
status Activity status of the WAL receiver process |
receive_start_lsn First write-ahead log location used when WAL receiver is started |
receive_start_tli First timeline number used when WAL receiver is started |
written_lsn Last write-ahead log location already received and written to disk, but not flushed. This should not be used for data integrity checks. |
flushed_lsn 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 |
received_tli 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 |
last_msg_send_time Send time of last message received from origin WAL sender |
last_msg_receipt_time Receipt time of last message received from origin WAL sender |
latest_end_lsn Last write-ahead log location reported to origin WAL sender |
latest_end_time Time of last write-ahead log location reported to origin WAL sender |
slot_name Replication slot name used by this WAL receiver |
sender_host Host of the PostgreSQL instance this WAL receiver is connected to. This can be a host name, an IP address, or a directory path if the connection is via Unix socket. (The path case can be distinguished because it will always be an absolute path, beginning with |
sender_port Port number of the PostgreSQL instance this WAL receiver is connected to. |
conninfo Connection string used by this WAL receiver, with security-sensitive fields obfuscated. |
: pg_stat_wal_receiver View
pg_stat_recovery_prefetch
The pg_stat_recovery_prefetch view will contain only one row. The columns wal_distance, block_distance and io_depth show current values, and the other columns show cumulative counters that can be reset with the pg_stat_reset_shared function.
Column Type Description |
|---|
stats_reset Time at which these statistics were last reset |
prefetch Number of blocks prefetched because they were not in the buffer pool |
hit Number of blocks not prefetched because they were already in the buffer pool |
skip_init Number of blocks not prefetched because they would be zero-initialized |
skip_new Number of blocks not prefetched because they didn't exist yet |
skip_fpw Number of blocks not prefetched because a full page image was included in the WAL |
skip_rep Number of blocks not prefetched because they were already recently prefetched |
wal_distance How many bytes ahead the prefetcher is looking |
block_distance How many blocks ahead the prefetcher is looking |
io_depth How many prefetches have been initiated but are not yet known to have completed |
: pg_stat_recovery_prefetch View
pg_stat_subscription
Column Type Description |
|---|
subid OID of the subscription |
subname Name of the subscription |
worker_type Type of the subscription worker process. Possible types are |
pid Process ID of the subscription worker process |
leader_pid Process ID of the leader apply worker if this process is a parallel apply worker; NULL if this process is a leader apply worker or a table synchronization worker |
relid OID of the relation that the worker is synchronizing; NULL for the leader apply worker and parallel apply workers |
received_lsn Last write-ahead log location received, the initial value of this field being 0; NULL for parallel apply workers |
last_msg_send_time Send time of last message received from origin WAL sender; NULL for parallel apply workers |
last_msg_receipt_time Receipt time of last message received from origin WAL sender; NULL for parallel apply workers |
latest_end_lsn Last write-ahead log location reported to origin WAL sender; NULL for parallel apply workers |
latest_end_time Time of last write-ahead log location reported to origin WAL sender; NULL for parallel apply workers |
: pg_stat_subscription View
pg_stat_subscription_stats
The pg_stat_subscription_stats view will contain one row per subscription.
Column Type Description |
|---|
subid OID of the subscription |
subname Name of the subscription |
apply_error_count Number of times an error occurred while applying changes. Note that any conflict resulting in an apply error will be counted in both |
sync_error_count Number of times an error occurred during the initial table synchronization |
confl_insert_exists Number of times a row insertion violated a |
confl_update_origin_differs Number of times an update was applied to a row that had been previously modified by another source during the application of changes. See update_origin_differs for details about this conflict. |
confl_update_exists Number of times that an updated row value violated a |
confl_update_missing Number of times the tuple to be updated was not found during the application of changes. See update_missing for details about this conflict. |
confl_delete_origin_differs Number of times a delete operation was applied to row that had been previously modified by another source during the application of changes. See delete_origin_differs for details about this conflict. |
confl_delete_missing Number of times the tuple to be deleted was not found during the application of changes. See delete_missing for details about this conflict. |
confl_multiple_unique_conflicts Number of times a row insertion or an updated row values violated multiple |
stats_reset Time at which these statistics were last reset |
: pg_stat_subscription_stats View
pg_stat_ssl
The pg_stat_ssl view will contain one row per backend or WAL sender process, showing statistics about SSL usage on this connection. It can be joined to pg_stat_activity or pg_stat_replication on the pid column to get more details about the connection.
Column Type Description |
|---|
pid Process ID of a backend or WAL sender process |
ssl True if SSL is used on this connection |
version Version of SSL in use, or NULL if SSL is not in use on this connection |
cipher Name of SSL cipher in use, or NULL if SSL is not in use on this connection |
bits Number of bits in the encryption algorithm used, or NULL if SSL is not used on this connection |
client_dn Distinguished Name (DN) field from the client certificate used, or NULL if no client certificate was supplied or if SSL is not in use on this connection. This field is truncated if the DN field is longer than |
client_serial Serial number of the client certificate, or NULL if no client certificate was supplied or if SSL is not in use on this connection. The combination of certificate serial number and certificate issuer uniquely identifies a certificate (unless the issuer erroneously reuses serial numbers). |
issuer_dn DN of the issuer of the client certificate, or NULL if no client certificate was supplied or if SSL is not in use on this connection. This field is truncated like client_dn. |
: pg_stat_ssl View
pg_stat_gssapi
The pg_stat_gssapi view will contain one row per backend, showing information about GSSAPI usage on this connection. It can be joined to pg_stat_activity or pg_stat_replication on the pid column to get more details about the connection.
Column Type Description |
|---|
pid Process ID of a backend |
gss_authenticated True if GSSAPI authentication was used for this connection |
principal Principal used to authenticate this connection, or NULL if GSSAPI was not used to authenticate this connection. This field is truncated if the principal is longer than |
encrypted True if GSSAPI encryption is in use on this connection |
credentials_delegated True if GSSAPI credentials were delegated on this connection. |
: pg_stat_gssapi View
pg_stat_archiver
The pg_stat_archiver view will always have a single row, containing data about the archiver process of the cluster.
Column Type Description |
|---|
archived_count Number of WAL files that have been successfully archived |
last_archived_wal Name of the WAL file most recently successfully archived |
last_archived_time Time of the most recent successful archive operation |
failed_count Number of failed attempts for archiving WAL files |
last_failed_wal Name of the WAL file of the most recent failed archival operation |
last_failed_time Time of the most recent failed archival operation |
stats_reset Time at which these statistics were last reset |
: pg_stat_archiver View
Normally, WAL files are archived in order, oldest to newest, but that is not guaranteed, and does not hold under special circumstances like when promoting a standby or after crash recovery. Therefore it is not safe to assume that all files older than last_archived_wal have also been successfully archived.
pg_stat_io
The pg_stat_io view will contain one row for each combination of backend type, target I/O object, and I/O context, showing cluster-wide I/O statistics. Combinations which do not make sense are omitted.
Currently, I/O on relations (e.g. tables, indexes) and WAL activity are tracked. However, relation I/O which bypasses shared buffers (e.g. when moving a table from one tablespace to another) is currently not tracked.
Column Type Description |
|---|
backend_type Type of backend (e.g. background worker, autovacuum worker). See pg_stat_activity for more information on |
object Target object of an I/O operation. Possible values are:
|
context The context of an I/O operation. Possible values are:
|
reads Number of read operations. |
read_bytes The total size of read operations in bytes. |
read_time Time spent waiting for read operations in milliseconds (if [track_io_timing (boolean)
|
writes Number of write operations. |
write_bytes The total size of write operations in bytes. |
write_time Time spent waiting for write operations in milliseconds (if [track_io_timing (boolean)
|
writebacks Number of units of size |
writeback_time Time spent waiting for writeback operations in milliseconds (if [track_io_timing (boolean)
|
extends Number of relation extend operations. |
extend_bytes The total size of relation extend operations in bytes. |
extend_time Time spent waiting for extend operations in milliseconds. (if [track_io_timing (boolean)
|
hits The number of times a desired block was found in a shared buffer. |
evictions Number of times a block has been written out from a shared or local buffer in order to make it available for another use. In |
reuses The number of times an existing buffer in a size-limited ring buffer outside of shared buffers was reused as part of an I/O operation in the |
fsyncs Number of |
fsync_time Time spent waiting for fsync operations in milliseconds (if [track_io_timing (boolean)
|
stats_reset Time at which these statistics were last reset. |
: pg_stat_io View
Some backend types never perform I/O operations on some I/O objects and/or in some I/O contexts. These rows are omitted from the view. For example, the checkpointer does not checkpoint temporary tables, so there will be no rows for backend_type checkpointer and object temp relation.
In addition, some I/O operations will never be performed either by certain backend types or on certain I/O objects and/or in certain I/O contexts. These cells will be NULL. For example, temporary tables are not fsynced, so fsyncs will be NULL for object temp relation. Also, the background writer does not perform reads, so reads will be NULL in rows for backend_type background writer.
For the object wal, fsyncs and fsync_time track the fsync activity of WAL files done in issue_xlog_fsync. writes and write_time track the write activity of WAL files done in XLogWrite. See WAL Configuration for more information.
pg_stat_io can be used to inform database tuning. For example:
-
A high
evictionscount can indicate that shared buffers should be increased. -
Client backends rely on the checkpointer to ensure data is persisted to permanent storage. Large numbers of
fsyncsbyclient backends could indicate a misconfiguration of shared buffers or of the checkpointer. More information on configuring the checkpointer can be found in WAL Configuration. -
Normally, client backends should be able to rely on auxiliary processes like the checkpointer and the background writer to write out dirty data as much as possible. Large numbers of writes by client backends could indicate a misconfiguration of shared buffers or of the checkpointer. More information on configuring the checkpointer can be found in WAL Configuration.
Columns tracking I/O wait time will only be non-zero when [track_io_timing (boolean)
track_io_timing configuration parameter](braised:ref/runtime-config-statistics#track-io-timing-boolean-track-io-timing-configuration-parameter) is enabled. The user should be careful when referencing these columns in combination with their corresponding I/O operations in case `track_io_timing` was not enabled for the entire time since the last stats reset.
pg_stat_bgwriter
The pg_stat_bgwriter view will always have a single row, containing data about the background writer of the cluster.
Column Type Description |
|---|
buffers_clean Number of buffers written by the background writer |
maxwritten_clean Number of times the background writer stopped a cleaning scan because it had written too many buffers |
buffers_alloc Number of buffers allocated |
stats_reset Time at which these statistics were last reset |
: pg_stat_bgwriter View
pg_stat_checkpointer
The pg_stat_checkpointer view will always have a single row, containing data about the checkpointer process of the cluster.
Column Type Description |
|---|
num_timed Number of scheduled checkpoints due to timeout |
num_requested Number of requested checkpoints |
num_done Number of checkpoints that have been performed |
restartpoints_timed Number of scheduled restartpoints due to timeout or after a failed attempt to perform it |
restartpoints_req Number of requested restartpoints |
restartpoints_done Number of restartpoints that have been performed |
write_time Total amount of time that has been spent in the portion of processing checkpoints and restartpoints where files are written to disk, in milliseconds |
sync_time Total amount of time that has been spent in the portion of processing checkpoints and restartpoints where files are synchronized to disk, in milliseconds |
buffers_written Number of shared buffers written during checkpoints and restartpoints |
slru_written Number of SLRU buffers written during checkpoints and restartpoints |
stats_reset Time at which these statistics were last reset |
: pg_stat_checkpointer View
Checkpoints may be skipped if the server has been idle since the last one. num_timed and num_requested count both completed and skipped checkpoints, while num_done tracks only the completed ones. Similarly, restartpoints may be skipped if the last replayed checkpoint record is already the last restartpoint. restartpoints_timed and restartpoints_req count both completed and skipped restartpoints, while restartpoints_done tracks only the completed ones.
pg_stat_wal
The pg_stat_wal view will always have a single row, containing data about WAL activity of the cluster.
Column Type Description |
|---|
wal_records Total number of WAL records generated |
wal_fpi Total number of WAL full page images generated |
wal_bytes Total amount of WAL generated in bytes |
wal_buffers_full Number of times WAL data was written to disk because WAL buffers became full |
stats_reset Time at which these statistics were last reset |
: pg_stat_wal View
pg_stat_database
The pg_stat_database view will contain one row for each database in the cluster, plus one for shared objects, showing database-wide statistics.
Column Type Description |
|---|
datid OID of this database, or 0 for objects belonging to a shared relation |
datname Name of this database, or |
numbackends Number of backends currently connected to this database, or |
xact_commit Number of transactions in this database that have been committed |
xact_rollback Number of transactions in this database that have been rolled back |
blks_read Number of disk blocks read in this database |
blks_hit Number of times disk blocks were found already in the buffer cache, so that a read was not necessary (this only includes hits in the PostgreSQL buffer cache, not the operating system's file system cache) |
tup_returned Number of live rows fetched by sequential scans and index entries returned by index scans in this database |
tup_fetched Number of live rows fetched by index scans in this database |
tup_inserted Number of rows inserted by queries in this database |
tup_updated Number of rows updated by queries in this database |
tup_deleted Number of rows deleted by queries in this database |
conflicts Number of queries canceled due to conflicts with recovery in this database. (Conflicts occur only on standby servers; see pg_stat_database_conflicts for details.) |
temp_files Number of temporary files created by queries in this database. All temporary files are counted, regardless of why the temporary file was created (e.g., sorting or hashing), and regardless of the [log_temp_files (integer)
|
temp_bytes Total amount of data written to temporary files by queries in this database. All temporary files are counted, regardless of why the temporary file was created, and regardless of the [log_temp_files (integer)
|
deadlocks Number of deadlocks detected in this database |
checksum_failures Number of data page checksum failures detected in this database (or on a shared object), or NULL if data checksums are disabled. |
checksum_last_failure Time at which the last data page checksum failure was detected in this database (or on a shared object), or NULL if data checksums are disabled. |
blk_read_time Time spent reading data file blocks by backends in this database, in milliseconds (if [track_io_timing (boolean)
|
blk_write_time Time spent writing data file blocks by backends in this database, in milliseconds (if [track_io_timing (boolean)
|
session_time Time spent by database sessions in this database, in milliseconds (note that statistics are only updated when the state of a session changes, so if sessions have been idle for a long time, this idle time won't be included) |
active_time Time spent executing SQL statements in this database, in milliseconds (this corresponds to the states |
idle_in_transaction_time Time spent idling while in a transaction in this database, in milliseconds (this corresponds to the states |
sessions Total number of sessions established to this database |
sessions_abandoned Number of database sessions to this database that were terminated because connection to the client was lost |
sessions_fatal Number of database sessions to this database that were terminated by fatal errors |
sessions_killed Number of database sessions to this database that were terminated by operator intervention |
parallel_workers_to_launch Number of parallel workers planned to be launched by queries on this database |
parallel_workers_launched Number of parallel workers launched by queries on this database |
stats_reset Time at which these statistics were last reset |
: pg_stat_database View
pg_stat_database_conflicts
The pg_stat_database_conflicts view will contain one row per database, showing database-wide statistics about query cancels occurring due to conflicts with recovery on standby servers. This view will only contain information on standby servers, since conflicts do not occur on primary servers.
Column Type Description |
|---|
datid OID of a database |
datname Name of this database |
confl_tablespace Number of queries in this database that have been canceled due to dropped tablespaces |
confl_lock Number of queries in this database that have been canceled due to lock timeouts |
confl_snapshot Number of queries in this database that have been canceled due to old snapshots |
confl_bufferpin Number of queries in this database that have been canceled due to pinned buffers |
confl_deadlock Number of queries in this database that have been canceled due to deadlocks |
confl_active_logicalslot Number of uses of logical slots in this database that have been canceled due to old snapshots or too low a [wal_level (enum)
|
: pg_stat_database_conflicts View
pg_stat_all_tables
The pg_stat_all_tables view will contain one row for each table in the current database (including TOAST tables), showing statistics about accesses to that specific table. The pg_stat_user_tables and pg_stat_sys_tables views contain the same information, but filtered to only show user and system tables respectively.
Column Type Description |
|---|
relid OID of a table |
schemaname Name of the schema that this table is in |
relname Name of this table |
seq_scan Number of sequential scans initiated on this table |
last_seq_scan The time of the last sequential scan on this table, based on the most recent transaction stop time |
seq_tup_read Number of live rows fetched by sequential scans |
idx_scan Number of index scans initiated on this table |
last_idx_scan The time of the last index scan on this table, based on the most recent transaction stop time |
idx_tup_fetch Number of live rows fetched by index scans |
n_tup_ins Total number of rows inserted |
n_tup_upd Total number of rows updated. (This includes row updates counted in n_tup_hot_upd and n_tup_newpage_upd, and remaining non-HOT updates.) |
n_tup_del Total number of rows deleted |
n_tup_hot_upd Number of rows HOT updated. These are updates where no successor versions are required in indexes. |
n_tup_newpage_upd Number of rows updated where the successor version goes onto a new heap page, leaving behind an original version with a t_ctid field that points to a different heap page. These are always non-HOT updates. |
n_live_tup Estimated number of live rows |
n_dead_tup Estimated number of dead rows |
n_mod_since_analyze Estimated number of rows modified since this table was last analyzed |
n_ins_since_vacuum Estimated number of rows inserted since this table was last vacuumed (not counting |
last_vacuum Last time at which this table was manually vacuumed (not counting |
last_autovacuum Last time at which this table was vacuumed by the autovacuum daemon |
last_analyze Last time at which this table was manually analyzed |
last_autoanalyze Last time at which this table was analyzed by the autovacuum daemon |
vacuum_count Number of times this table has been manually vacuumed (not counting |
autovacuum_count Number of times this table has been vacuumed by the autovacuum daemon |
analyze_count Number of times this table has been manually analyzed |
autoanalyze_count Number of times this table has been analyzed by the autovacuum daemon |
total_vacuum_time Total time this table has been manually vacuumed, in milliseconds (not counting |
total_autovacuum_time Total time this table has been vacuumed by the autovacuum daemon, in milliseconds. (This includes the time spent sleeping due to cost-based delays.) |
total_analyze_time Total time this table has been manually analyzed, in milliseconds. (This includes the time spent sleeping due to cost-based delays.) |
total_autoanalyze_time Total time this table has been analyzed by the autovacuum daemon, in milliseconds. (This includes the time spent sleeping due to cost-based delays.) |
: pg_stat_all_tables View
pg_stat_all_indexes
The pg_stat_all_indexes view will contain one row for each index in the current database, showing statistics about accesses to that specific index. The pg_stat_user_indexes and pg_stat_sys_indexes views contain the same information, but filtered to only show user and system indexes respectively.
Column Type Description |
|---|
relid OID of the table for this index |
indexrelid OID of this index |
schemaname Name of the schema this index is in |
relname Name of the table for this index |
indexrelname Name of this index |
idx_scan Number of index scans initiated on this index |
last_idx_scan The time of the last scan on this index, based on the most recent transaction stop time |
idx_tup_read Number of index entries returned by scans on this index |
idx_tup_fetch Number of live table rows fetched by simple index scans using this index |
: pg_stat_all_indexes View
Indexes can be used by simple index scans, "bitmap" index scans, and the optimizer. In a bitmap scan the output of several indexes can be combined via AND or OR rules, so it is difficult to associate individual heap row fetches with specific indexes when a bitmap scan is used. Therefore, a bitmap scan increments the pg_stat_all_indexes.idx_tup_read count(s) for the index(es) it uses, and it increments the pg_stat_all_tables.idx_tup_fetch count for the table, but it does not affect pg_stat_all_indexes.idx_tup_fetch. The optimizer also accesses indexes to check for supplied constants whose values are outside the recorded range of the optimizer statistics because the optimizer statistics might be stale.
The idx_tup_read and idx_tup_fetch counts can be different even without any use of bitmap scans, because idx_tup_read counts index entries retrieved from the index while idx_tup_fetch counts live rows fetched from the table. The latter will be less if any dead or not-yet-committed rows are fetched using the index, or if any heap fetches are avoided by means of an index-only scan.
Index scans may sometimes perform multiple index searches per execution. Each index search increments pg_stat_all_indexes.idx_scan, so it's possible for the count of index scans to significantly exceed the total number of index scan executor node executions.
This can happen with queries that use certain SQL constructs to search for rows matching any value out of a list or array of multiple scalar values (see Row and Array Comparisons). It can also happen to queries with a column_name = value1 OR column_name = value2 ... construct, though only when the optimizer transforms the construct into an equivalent multi-valued array representation. Similarly, when B-tree index scans use the skip scan optimization, an index search is performed each time the scan is repositioned to the next index leaf page that might have matching tuples (see Multicolumn Indexes).
EXPLAIN ANALYZE outputs the total number of index searches performed by each index scan node. See EXPLAIN ANALYZE for an example demonstrating how this works.
pg_statio_all_tables
The pg_statio_all_tables view will contain one row for each table in the current database (including TOAST tables), showing statistics about I/O on that specific table. The pg_statio_user_tables and pg_statio_sys_tables views contain the same information, but filtered to only show user and system tables respectively.
Column Type Description |
|---|
relid OID of a table |
schemaname Name of the schema that this table is in |
relname Name of this table |
heap_blks_read Number of disk blocks read from this table |
heap_blks_hit Number of buffer hits in this table |
idx_blks_read Number of disk blocks read from all indexes on this table |
idx_blks_hit Number of buffer hits in all indexes on this table |
toast_blks_read Number of disk blocks read from this table's TOAST table (if any) |
toast_blks_hit Number of buffer hits in this table's TOAST table (if any) |
tidx_blks_read Number of disk blocks read from this table's TOAST table indexes (if any) |
tidx_blks_hit Number of buffer hits in this table's TOAST table indexes (if any) |
: pg_statio_all_tables View
pg_statio_all_indexes
The pg_statio_all_indexes view will contain one row for each index in the current database, showing statistics about I/O on that specific index. The pg_statio_user_indexes and pg_statio_sys_indexes views contain the same information, but filtered to only show user and system indexes respectively.
Column Type Description |
|---|
relid OID of the table for this index |
indexrelid OID of this index |
schemaname Name of the schema this index is in |
relname Name of the table for this index |
indexrelname Name of this index |
idx_blks_read Number of disk blocks read from this index |
idx_blks_hit Number of buffer hits in this index |
: pg_statio_all_indexes View
pg_statio_all_sequences
The pg_statio_all_sequences view will contain one row for each sequence in the current database, showing statistics about I/O on that specific sequence.
Column Type Description |
|---|
relid OID of a sequence |
schemaname Name of the schema this sequence is in |
relname Name of this sequence |
blks_read Number of disk blocks read from this sequence |
blks_hit Number of buffer hits in this sequence |
: pg_statio_all_sequences View
pg_stat_user_functions
The pg_stat_user_functions view will contain one row for each tracked function, showing statistics about executions of that function. The [track_functions (enum)
track_functions configuration parameter](braised:ref/runtime-config-statistics#track-functions-enum-track-functions-configuration-parameter) parameter controls exactly which functions are tracked.
Column Type Description |
|---|
funcid OID of a function |
schemaname Name of the schema this function is in |
funcname Name of this function |
calls Number of times this function has been called |
total_time Total time spent in this function and all other functions called by it, in milliseconds |
self_time Total time spent in this function itself, not including other functions called by it, in milliseconds |
: pg_stat_user_functions View
pg_stat_slru
PostgreSQL accesses certain on-disk information via SLRU (simple least-recently-used) caches. The pg_stat_slru view will contain one row for each tracked SLRU cache, showing statistics about access to cached pages.
For each SLRU cache that's part of the core server, there is a configuration parameter that controls its size, with the suffix _buffers appended.
Column Type Description |
|---|
name Name of the SLRU |
blks_zeroed Number of blocks zeroed during initializations |
blks_hit Number of times disk blocks were found already in the SLRU, so that a read was not necessary (this only includes hits in the SLRU, not the operating system's file system cache) |
blks_read Number of disk blocks read for this SLRU |
blks_written Number of disk blocks written for this SLRU |
blks_exists Number of blocks checked for existence for this SLRU |
flushes Number of flushes of dirty data for this SLRU |
truncates Number of truncates for this SLRU |
stats_reset Time at which these statistics were last reset |
: pg_stat_slru View
Statistics Functions
Other ways of looking at the statistics can be set up by writing queries that use the same underlying statistics access functions used by the standard views shown above. For details such as the functions' names, consult the definitions of the standard views. (For example, in psql you could issue \d+ pg_stat_activity.) The access functions for per-database statistics take a database OID as an argument to identify which database to report on. The per-table and per-index functions take a table or index OID. The functions for per-function statistics take a function OID. Note that only tables, indexes, and functions in the current database can be seen with these functions.
Additional functions related to the cumulative statistics system are listed in Additional Statistics Functions.
Function Description |
|---|
Returns the process ID of the server process attached to the current session. |
Returns I/O statistics about the backend with the specified process ID. The output fields are exactly the same as the ones in the pg_stat_io view. The function does not return I/O statistics for the checkpointer, the background writer, the startup process and the autovacuum launcher as they are already visible in the pg_stat_io view and there is only one of each. |
Returns a record of information about the backend with the specified process ID, or one record for each active backend in the system if |
Returns WAL statistics about the backend with the specified process ID. The output fields are exactly the same as the ones in the pg_stat_wal view. The function does not return WAL statistics for the checkpointer, the background writer, the startup process and the autovacuum launcher. |
Returns the timestamp of the current statistics snapshot, or NULL if no statistics snapshot has been taken. A snapshot is taken the first time cumulative statistics are accessed in a transaction if |
Returns the number of block read requests for table or index, in the current transaction. This number minus |
Returns the number of block read requests for table or index, in the current transaction, found in cache (not triggering kernel |
Discards the current statistics snapshot or cached information. |
Resets all statistics counters for the current database to zero. This function is restricted to superusers by default, but other users can be granted EXECUTE to run the function. |
Resets some cluster-wide statistics counters to zero, depending on the argument.
This function is restricted to superusers by default, but other users can be granted EXECUTE to run the function. |
Resets statistics for a single table or index in the current database or shared across all databases in the cluster to zero. This function is restricted to superusers by default, but other users can be granted EXECUTE to run the function. |
Resets statistics for a single backend with the specified process ID to zero. This function is restricted to superusers by default, but other users can be granted EXECUTE to run the function. |
Resets statistics for a single function in the current database to zero. This function is restricted to superusers by default, but other users can be granted EXECUTE to run the function. |
Resets statistics to zero for a single SLRU cache, or for all SLRUs in the cluster. If This function is restricted to superusers by default, but other users can be granted EXECUTE to run the function. |
Resets statistics of the replication slot defined by the argument. If the argument is This function is restricted to superusers by default, but other users can be granted EXECUTE to run the function. |
Resets statistics for a single subscription shown in the pg_stat_subscription_stats view to zero. If the argument is This function is restricted to superusers by default, but other users can be granted EXECUTE to run the function. |
: Additional Statistics Functions
Using pg_stat_reset() also resets counters that autovacuum uses to determine when to trigger a vacuum or an analyze. Resetting these counters can cause autovacuum to not perform necessary work, which can cause problems such as table bloat or out-dated table statistics. A database-wide ANALYZE is recommended after the statistics have been reset.
pg_stat_get_activity, the underlying function of the pg_stat_activity view, returns a set of records containing all the available information about each backend process.
Sometimes it may be more convenient to obtain just a subset of this information.
In such cases, another set of per-backend statistics access functions can be used; these are shown in Per-Backend Statistics Functions.
These access functions use the session's backend ID number, which is a small integer (>= 0) that is distinct from the backend ID of any concurrent session, although a session's ID can be recycled as soon as it exits.
The backend ID is used, among other things, to identify the session's temporary schema if it has one.
The function pg_stat_get_backend_idset provides a convenient way to list all the active backends' ID numbers for invoking these functions.
For example, to show the PIDs and current queries of all backends:
SELECT pg_stat_get_backend_pid(backendid) AS pid,
pg_stat_get_backend_activity(backendid) AS query
FROM pg_stat_get_backend_idset() AS backendid;
Function Description |
|---|
Returns the text of this backend's most recent query. |
Returns the time when the backend's most recent query was started. |
Returns the IP address of the client connected to this backend. |
Returns the TCP port number that the client is using for communication. |
Returns the OID of the database this backend is connected to. |
Returns the set of currently active backend ID numbers. |
Returns the process ID of this backend. |
Returns the time when this process was started. |
Returns a record of information about the subtransactions of the backend with the specified ID. The fields returned are |
Returns the OID of the user logged into this backend. |
Returns the wait event name if this backend is currently waiting, otherwise NULL. See Wait Events of Type through Wait Events of Type . |
Returns the wait event type name if this backend is currently waiting, otherwise NULL. See Wait Event Types for details. |
Returns the time when the backend's current transaction was started. |
: Per-Backend Statistics Functions