Wiki / Statistics & Metrics / pg_stat_progress_vacuum
pg_stat_progress_vacuum.heap_blks_scanned
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 …
Reading PostgreSQL 18.6.
Description
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 the vacuum is complete. This counter only advances when the phase is scanning heap.
- View
- pg_stat_progress_vacuum
- Field
- heap_blks_scanned
- SQL type
- bigint
- Units named in the field definition
- blocks
- Reset observation
- No stats_reset field is documented for this view
Usage
SELECT heap_blks_scanned FROM pg_catalog.pg_stat_progress_vacuum;View semantics
Whenever VACUUM is running, the pg_stat_progress_vacuum view will contain one row for each backend (including autovacuum worker processes) that is currently vacuuming. The tables below describe the information that will be reported and provide information about how to interpret it. Progress for VACUUM FULL commands is reported via pg_stat_progress_cluster because both VACUUM FULL and CLUSTER rewrite the table, while regular VACUUM only modifies it in place. See Section 27.4.2.
Collection and reset context
Read the same-version statistics collection and view documentation below for reset scope and visibility. No per-field reset rule is inferred from the field name.
Inspect this field
Example query; no execution result or measured value is asserted.
SELECT heap_blks_scanned FROM pg_catalog.pg_stat_progress_vacuum;Related entries
Documentation and source
Source build
- Version
- 18.6
- Build
- https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2
- Source fingerprint
555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f
Compare versions
PostgreSQL 17 → 18: unchanged.
Compares recorded interfaces and attributes. Source fingerprints and build metadata are excluded; an absent sample is not proof of the introduction or removal release.
Related entries
pg_stat_progress_vacuum.datidpg_stat_progress_vacuum.datnamepg_stat_progress_vacuum.dead_tuple_bytespg_stat_progress_vacuum.delay_timepg_stat_progress_vacuum.heap_blks_totalpg_stat_progress_vacuum.heap_blks_vacuumedpg_stat_progress_vacuum.index_vacuum_countpg_stat_progress_vacuum.indexes_processedpg_stat_progress_vacuum.indexes_totalpg_stat_progress_vacuum.max_dead_tuple_bytespg_stat_progress_vacuum.num_dead_item_idspg_stat_progress_vacuum.phase
Export JSON · Back to Statistics & Metrics · Recorded in PostgreSQL 10 through 20; the first sample is not necessarily its introduction.