{"Entry":{"collection":"metric","key":"pg_stat_progress_vacuum-max_dead_tuples","name":"pg_stat_progress_vacuum.max_dead_tuples","aliases":["max_dead_tuples","pg_stat_progress_vacuum"],"metadata":{"aliases":["max_dead_tuples","pg_stat_progress_vacuum"],"category":"pg_stat_progress_vacuum","content_hash":"145d82f62bd56aaf300b01e31cc420809beed438287006d21286f022cf7ba27a","imported_at":"2026-09-30T00:40:45.98759+08:00","name":"pg_stat_progress_vacuum.max_dead_tuples","name_zh":"","slug":"pg_stat_progress_vacuum-max_dead_tuples","summary":"Number of dead tuples that we can store before needing to perform an index vacuum cycle, based on maintenance_work_mem."}},"Definition":{"Collection":"metric","Key":"pg_stat_progress_vacuum-max_dead_tuples","SourceDatabase":"center","Version":"16","SourceTable":"statistics_metric","SourceKey":"pg_stat_progress_vacuum-max_dead_tuples","SourceRevision":"c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed","Facts":{"comparison_data":{"field":"max_dead_tuples","sql_type":"bigint","units_mentioned":["tuples"],"view":"pg_stat_progress_vacuum"},"comparison_hash":"e497e3573f229d875efb6dc274fb5c04e1e82ec98998c505e0425c5ed61606c8","description":["Number of dead tuples that we can store before needing to perform an index vacuum cycle, based on maintenance_work_mem."],"documented":true,"facts":[{"label":"View","value":"pg_stat_progress_vacuum"},{"label":"Field","value":"max_dead_tuples"},{"label":"SQL type","value":"bigint"},{"label":"Units named in the field definition","value":"tuples"},{"label":"Reset observation","value":"No stats_reset field is documented for this view"}],"field":"max_dead_tuples","manual_html":"","manual_path":"/docs/16/progress-reporting.html","related":[{"label":"pg_stat_progress_vacuum columns","url":"/wiki/catalog/pg_stat_progress_vacuum/?v=16"},{"label":"Statistics collection and reset functions","url":"/docs/16/monitoring-stats.html"}],"release":{"channel":"stable","label":"16.15","major":"16","ref":"https://ftp.postgresql.org/pub/source/v16.15/postgresql-16.15.tar.bz2","revision":"c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed"},"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 28.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 max_dead_tuples FROM pg_catalog.pg_stat_progress_vacuum;","paragraphs":["Example query; no execution result or measured value is asserted."],"title":"Inspect this field"}],"signature":"SELECT max_dead_tuples FROM pg_catalog.pg_stat_progress_vacuum;","source_only":false,"sources":[{"label":"PostgreSQL 16 English manual","path":"progress-reporting.html","sha256":"2b460ce06a91510e6d57a1e5d51b3ffdb65426fb38d30b0ff2774af6da50cf68","url":"/docs/16/progress-reporting.html#PG-STAT-PROGRESS-VACUUM-VIEW"}],"sql_type":"bigint","tables":[],"units_mentioned":["tuples"],"view":"pg_stat_progress_vacuum"},"ManualEvidence":{"manual_path":"/docs/16/progress-reporting.html","release":{"channel":"stable","label":"16.15","major":"16","ref":"https://ftp.postgresql.org/pub/source/v16.15/postgresql-16.15.tar.bz2","revision":"c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed"},"sources":[{"label":"PostgreSQL 16 English manual","path":"progress-reporting.html","sha256":"2b460ce06a91510e6d57a1e5d51b3ffdb65426fb38d30b0ff2774af6da50cf68","url":"/docs/16/progress-reporting.html#PG-STAT-PROGRESS-VACUUM-VIEW"}]},"MeasuredEvidence":{}},"Text":{"Collection":"metric","Key":"pg_stat_progress_vacuum-max_dead_tuples","SourceDatabase":"center","Version":"16","Locale":"en","Title":"pg_stat_progress_vacuum.max_dead_tuples","Summary":"Number of dead tuples that we can store before needing to perform an index vacuum cycle, based on maintenance_work_mem.","BodyHTML":"\u003cp\u003eNumber of dead tuples that we can store before needing to perform an index vacuum cycle, based on maintenance_work_mem.\u003c/p\u003e","SourceRevision":"c1575341fa7bd40f5274ea465b34390f4dc64cdd0770af327005caaeb9f6b7ed","ContentHash":"02c4cd0d6c66e0e7cde94895b0b563702a3beaa454ce7f0a7bde2f16d2ab1e84","Payload":{"description":["Number of dead tuples that we can store before needing to perform an index vacuum cycle, based on maintenance_work_mem."],"manual_html":"","related":[{"label":"pg_stat_progress_vacuum columns","url":"/wiki/catalog/pg_stat_progress_vacuum/?v=16"},{"label":"Statistics collection and reset functions","url":"/docs/16/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 28.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 max_dead_tuples 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"],"Locales":["en"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}