Wiki / Statistics & Metrics
Statistics & Metrics
Compare versionsIndividually addressable statistics and progress fields, definitions, units and reset context.
Reading PostgreSQL 18.6.
616 entries; 514 recorded in PostgreSQL 18.6.
-
pg_stat_progress_basebackup.tablespaces_streamed pg_stat_progress_basebackup
Number of tablespaces streamed. This counter only advances when the phase is streaming database files.
-
pg_stat_progress_basebackup.tablespaces_total pg_stat_progress_basebackup
Total number of tablespaces that will be streamed.
-
pg_stat_progress_cluster.cluster_index_relid pg_stat_progress_cluster
If the table is being scanned using an index, this is the OID of the index being used; otherwise, it is zero.
-
pg_stat_progress_cluster.command pg_stat_progress_cluster
The command that is running. Either CLUSTER or VACUUM FULL.
-
pg_stat_progress_cluster.datid pg_stat_progress_cluster
OID of the database to which this backend is connected.
-
pg_stat_progress_cluster.datname pg_stat_progress_cluster
Name of the database to which this backend is connected.
-
pg_stat_progress_cluster.heap_blks_scanned pg_stat_progress_cluster
Number of heap blocks scanned. This counter only advances when the phase is seq scanning heap.
-
pg_stat_progress_cluster.heap_blks_total pg_stat_progress_cluster
Total number of heap blocks in the table. This number is reported as of the beginning of seq scanning heap.
-
pg_stat_progress_cluster.heap_tuples_scanned pg_stat_progress_cluster
Number of heap tuples scanned. This counter only advances when the phase is seq scanning heap, index scanning heap or writing new heap.
-
pg_stat_progress_cluster.heap_tuples_written pg_stat_progress_cluster
Number of heap tuples written. This counter only advances when the phase is seq scanning heap, index scanning heap or writing new heap.
-
pg_stat_progress_cluster.index_rebuild_count pg_stat_progress_cluster
Number of indexes rebuilt. This counter only advances when the phase is rebuilding index.
-
pg_stat_progress_cluster.phase pg_stat_progress_cluster
Current processing phase. See Table 27.41.
-
pg_stat_progress_cluster.pid pg_stat_progress_cluster
Process ID of backend.
-
pg_stat_progress_cluster.relid pg_stat_progress_cluster
OID of the table being clustered.
-
pg_stat_progress_copy.bytes_processed pg_stat_progress_copy
Number of bytes already processed by COPY command.
-
pg_stat_progress_copy.bytes_total pg_stat_progress_copy
Size of source file for COPY FROM command in bytes. It is set to 0 if not available.
-
pg_stat_progress_copy.command pg_stat_progress_copy
The command that is running: COPY FROM, or COPY TO.
-
pg_stat_progress_copy.datid pg_stat_progress_copy
OID of the database to which this backend is connected.
-
pg_stat_progress_copy.datname pg_stat_progress_copy
Name of the database to which this backend is connected.
-
pg_stat_progress_copy.pid pg_stat_progress_copy
Process ID of backend.
-
pg_stat_progress_copy.relid pg_stat_progress_copy
OID of the table on which the COPY command is executed. It is set to 0 if copying from a SELECT query.
-
pg_stat_progress_copy.tuples_excluded pg_stat_progress_copy
Number of tuples not processed because they were excluded by the WHERE clause of the COPY command.
-
pg_stat_progress_copy.tuples_processed pg_stat_progress_copy
Number of tuples already processed by COPY command.
-
pg_stat_progress_copy.tuples_skipped pg_stat_progress_copy
Number of tuples skipped because they contain malformed data. This counter only advances when a value other than stop is specified to the ON_ERROR option.
-
pg_stat_progress_copy.type pg_stat_progress_copy
The I/O type that the data is read from or written to: FILE, PROGRAM, PIPE (for COPY FROM STDIN and COPY TO STDOUT), or CALLBACK (used for example during the initial table synchronization in logical replication).
-
pg_stat_progress_create_index.blocks_done pg_stat_progress_create_index
Number of blocks already processed in the current phase.
-
pg_stat_progress_create_index.blocks_total pg_stat_progress_create_index
Total number of blocks to be processed in the current phase.
-
pg_stat_progress_create_index.command pg_stat_progress_create_index
Specific command type: CREATE INDEX, CREATE INDEX CONCURRENTLY, REINDEX, or REINDEX CONCURRENTLY.
-
pg_stat_progress_create_index.current_locker_pid pg_stat_progress_create_index
Process ID of the locker currently being waited for.
-
pg_stat_progress_create_index.datid pg_stat_progress_create_index
OID of the database to which this backend is connected.
-
pg_stat_progress_create_index.datname pg_stat_progress_create_index
Name of the database to which this backend is connected.
-
pg_stat_progress_create_index.index_relid pg_stat_progress_create_index
OID of the index being created or reindexed. During a non-concurrent CREATE INDEX, this is 0.
-
pg_stat_progress_create_index.lockers_done pg_stat_progress_create_index
Number of lockers already waited for.
-
pg_stat_progress_create_index.lockers_total pg_stat_progress_create_index
Total number of lockers to wait for, when applicable.
-
pg_stat_progress_create_index.partitions_done pg_stat_progress_create_index
Number of partitions on which the index has already been created or attached, including both direct and indirect partitions. 0 during a REINDEX, or when the index is not partitioned.
-
pg_stat_progress_create_index.partitions_total pg_stat_progress_create_index
Total number of partitions on which the index is to be created or attached, including both direct and indirect partitions. 0 during a REINDEX, or when the index is not partitioned.
-
pg_stat_progress_create_index.phase pg_stat_progress_create_index
Current processing phase of index creation. See Table 27.44.
-
pg_stat_progress_create_index.pid pg_stat_progress_create_index
Process ID of the backend creating indexes.
-
pg_stat_progress_create_index.relid pg_stat_progress_create_index
OID of the table on which the index is being created.
-
pg_stat_progress_create_index.tuples_done pg_stat_progress_create_index
Number of tuples already processed in the current phase.
-
pg_stat_progress_create_index.tuples_total pg_stat_progress_create_index
Total number of tuples to be processed in the current phase.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
pg_stat_progress_vacuum.datid pg_stat_progress_vacuum
OID of the database to which this backend is connected.
-
pg_stat_progress_vacuum.datname pg_stat_progress_vacuum
Name of the database to which this backend is connected.
-
pg_stat_progress_vacuum.dead_tuple_bytes pg_stat_progress_vacuum
Amount of dead tuple data collected since the last index vacuum cycle.
-
pg_stat_progress_vacuum.delay_time pg_stat_progress_vacuum
Total time spent sleeping due to cost-based delay (see Section 19.10.2), in milliseconds (if track_cost_delay_timing is enabled, otherwise zero). This includes the time that any associated parallel workers have slept. However, parallel workers repor…
-
pg_stat_progress_vacuum.heap_blks_scanned pg_stat_progress_vacuum
Number of heap blocks scanned. Because the visibility map is used to optimize scans, some blocks will be skipped without inspection; skipped blocks are included in this total, so that this number will eventually become equal to heap_blks_total when …
-
pg_stat_progress_vacuum.heap_blks_total pg_stat_progress_vacuum
Total number of heap blocks in the table. This number is reported as of the beginning of the scan; blocks added later will not be (and need not be) visited by this VACUUM.
-
pg_stat_progress_vacuum.heap_blks_vacuumed pg_stat_progress_vacuum
Number of heap blocks vacuumed. Unless the table has no indexes, this counter only advances when the phase is vacuuming heap. Blocks that contain no dead tuples are skipped, so the counter may sometimes skip forward in large increments.
-
pg_stat_progress_vacuum.index_vacuum_count pg_stat_progress_vacuum
Number of completed index vacuum cycles.
-
pg_stat_progress_vacuum.indexes_processed pg_stat_progress_vacuum
Number of indexes processed. This counter only advances when the phase is vacuuming indexes or cleaning up indexes.
-
pg_stat_progress_vacuum.indexes_total pg_stat_progress_vacuum
Total number of indexes that will be vacuumed or cleaned up. This number is reported at the beginning of the vacuuming indexes phase or the cleaning up indexes phase.
-
pg_stat_progress_vacuum.max_dead_tuple_bytes pg_stat_progress_vacuum
Amount of dead tuple data that we can store before needing to perform an index vacuum cycle, based on maintenance_work_mem.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
pg_stat_progress_vacuum.num_dead_item_ids pg_stat_progress_vacuum
Number of dead item identifiers collected since the last index vacuum cycle.
-
Not recorded in the selected version.
-
pg_stat_progress_vacuum.phase pg_stat_progress_vacuum
Current processing phase of vacuum. See Table 27.46.
-
pg_stat_progress_vacuum.pid pg_stat_progress_vacuum
Process ID of backend.
-
pg_stat_progress_vacuum.relid pg_stat_progress_vacuum
OID of the table being vacuumed.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
Not recorded in the selected version.
-
pg_stat_recovery_prefetch.block_distance pg_stat_recovery_prefetch
How many blocks ahead the prefetcher is looking
-
pg_stat_recovery_prefetch.hit pg_stat_recovery_prefetch
Number of blocks not prefetched because they were already in the buffer pool
-
pg_stat_recovery_prefetch.io_depth pg_stat_recovery_prefetch
How many prefetches have been initiated but are not yet known to have completed
-
pg_stat_recovery_prefetch.prefetch pg_stat_recovery_prefetch
Number of blocks prefetched because they were not in the buffer pool
-
pg_stat_recovery_prefetch.skip_fpw pg_stat_recovery_prefetch
Number of blocks not prefetched because a full page image was included in the WAL
-
pg_stat_recovery_prefetch.skip_init pg_stat_recovery_prefetch
Number of blocks not prefetched because they would be zero-initialized
-
pg_stat_recovery_prefetch.skip_new pg_stat_recovery_prefetch
Number of blocks not prefetched because they didn't exist yet
RecordedFirst recordedInterface or attribute changeNo longer recorded
Squares indicate presence in sampled builds, not first introduction. Select a square for the same-version definition and sources.
Changes in PostgreSQL 18.6 · Export JSON
Reading this collection
Each field retains its view and source context. Units, collection and reset behavior are recorded only where supported by evidence. Example queries do not assert measured values, and current-state fields must not be treated as cumulative counters.