{"Entry":{"collection":"metric","key":"pg_stat_progress_vacuum-heap_blks_scanned","name":"pg_stat_progress_vacuum.heap_blks_scanned","aliases":["heap_blks_scanned","pg_stat_progress_vacuum"],"metadata":{"aliases":["heap_blks_scanned","pg_stat_progress_vacuum"],"category":"pg_stat_progress_vacuum","content_hash":"4dc2558b3a11ea1b003519ced3474de638ab7e9192c08c81b02dff662d373f30","imported_at":"2026-09-30T00:40:45.967856+08:00","name":"pg_stat_progress_vacuum.heap_blks_scanned","name_zh":"","slug":"pg_stat_progress_vacuum-heap_blks_scanned","summary":"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."}},"Definition":{"Collection":"metric","Key":"pg_stat_progress_vacuum-heap_blks_scanned","SourceDatabase":"center","Version":"18","SourceTable":"statistics_metric","SourceKey":"pg_stat_progress_vacuum-heap_blks_scanned","SourceRevision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","Facts":{"comparison_data":{"field":"heap_blks_scanned","sql_type":"bigint","units_mentioned":["blocks"],"view":"pg_stat_progress_vacuum"},"comparison_hash":"55ebf3eb71701700d4a2fcb1d1cc7ca0efebd7fe0ab3470f44f04a037a4eb1a4","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."],"documented":true,"facts":[{"label":"View","value":"pg_stat_progress_vacuum"},{"label":"Field","value":"heap_blks_scanned"},{"label":"SQL type","value":"bigint"},{"label":"Units named in the field definition","value":"blocks"},{"label":"Reset observation","value":"No stats_reset field is documented for this view"}],"field":"heap_blks_scanned","manual_html":"","manual_path":"/docs/18/progress-reporting.html","related":[{"label":"pg_stat_progress_vacuum columns","url":"/wiki/catalog/pg_stat_progress_vacuum/?v=18"},{"label":"Statistics collection and reset functions","url":"/docs/18/monitoring-stats.html"}],"release":{"channel":"stable","label":"18.6","major":"18","ref":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2","revision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"},"sections":[{"paragraphs":["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."],"title":"View semantics"},{"paragraphs":["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."],"title":"Collection and reset context"},{"code":"SELECT heap_blks_scanned FROM pg_catalog.pg_stat_progress_vacuum;","paragraphs":["Example query; no execution result or measured value is asserted."],"title":"Inspect this field"}],"signature":"SELECT heap_blks_scanned FROM pg_catalog.pg_stat_progress_vacuum;","source_only":false,"sources":[{"label":"PostgreSQL 18 English manual","path":"progress-reporting.html","sha256":"a1f46d2b670502bfe75f1cf5192050ef2ef68202a8f928c4915abea0f4f71ae6","url":"/docs/18/progress-reporting.html#PG-STAT-PROGRESS-VACUUM-VIEW"}],"sql_type":"bigint","tables":[],"units_mentioned":["blocks"],"view":"pg_stat_progress_vacuum"},"ManualEvidence":{"manual_path":"/docs/18/progress-reporting.html","release":{"channel":"stable","label":"18.6","major":"18","ref":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2","revision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"},"sources":[{"label":"PostgreSQL 18 English manual","path":"progress-reporting.html","sha256":"a1f46d2b670502bfe75f1cf5192050ef2ef68202a8f928c4915abea0f4f71ae6","url":"/docs/18/progress-reporting.html#PG-STAT-PROGRESS-VACUUM-VIEW"}]},"MeasuredEvidence":{}},"Text":{"Collection":"metric","Key":"pg_stat_progress_vacuum-heap_blks_scanned","SourceDatabase":"center","Version":"18","Locale":"en","Title":"pg_stat_progress_vacuum.heap_blks_scanned","Summary":"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.","BodyHTML":"\u003cp\u003eNumber 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.\u003c/p\u003e","SourceRevision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","ContentHash":"8322d9c298f312199c203d5ea5765cbb9739bd4518e54bd941e1da7a4b59dfd7","Payload":{"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."],"manual_html":"","related":[{"label":"pg_stat_progress_vacuum columns","url":"/wiki/catalog/pg_stat_progress_vacuum/?v=18"},{"label":"Statistics collection and reset functions","url":"/docs/18/monitoring-stats.html"}],"sections":[{"paragraphs":["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."],"title":"View semantics"},{"paragraphs":["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."],"title":"Collection and reset context"},{"code":"SELECT heap_blks_scanned FROM pg_catalog.pg_stat_progress_vacuum;","paragraphs":["Example query; no execution result or measured value is asserted."],"title":"Inspect this field"}],"tables":[]}},"RequestedLocale":"zh-Hans","Fallback":true,"Versions":["10","11","12","13","14","15","16","17","18","19","20"],"Locales":["en"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}