{"kind": "metric", "major": "18", "item": {"slug": "pg_stat_progress_vacuum-mode", "name": "pg_stat_progress_vacuum.mode", "name_zh": "", "category": "pg_stat_progress_vacuum", "summary": "Not recorded in the selected version.", "aliases": ["mode", "pg_stat_progress_vacuum"], "content_hash": "7fbd082066ab393b4a9aee97b31440fb3adf7c24d425148e89ebbb15f0d5b1a1", "versions": {"19": {"view": "pg_stat_progress_vacuum", "facts": [{"label": "View", "value": "pg_stat_progress_vacuum"}, {"label": "Field", "value": "mode"}, {"label": "SQL type", "value": "text"}, {"label": "Units named in the field definition", "value": "Not specified"}, {"label": "Reset observation", "value": "No stats_reset field is documented for this view"}], "field": "mode", "tables": [], "related": [{"url": "/wiki/catalog/pg_stat_progress_vacuum/?v=19", "label": "pg_stat_progress_vacuum columns"}, {"url": "/docs/19/monitoring-stats.html", "label": "Statistics collection and reset functions"}], "release": {"ref": "https://ftp.postgresql.org/pub/source/v19beta4/postgresql-19beta4.tar.bz2", "label": "19beta4", "major": "19", "channel": "preview", "revision": "83157ee9c599d03b2f7a3d73ef3a56ec24e0e79cc2b3501a64d1364f56398c86"}, "sources": [{"url": "/docs/19/progress-reporting.html#PG-STAT-PROGRESS-VACUUM-VIEW", "path": "progress-reporting.html", "label": "PostgreSQL 19 English manual", "sha256": "911eea089109c945679f9ac5c21a3b1b7c9186237acec4639f23861e931e24cc"}], "sections": [{"title": "View semantics", "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_repack, and is also visible via the backwards-compatibility 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.5 and Section 27.4.2."]}, {"title": "Collection and reset context", "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."]}, {"code": "SELECT mode FROM pg_catalog.pg_stat_progress_vacuum;", "title": "Inspect this field", "paragraphs": ["Example query; no execution result or measured value is asserted."]}], "sql_type": "text", "signature": "SELECT mode FROM pg_catalog.pg_stat_progress_vacuum;", "documented": true, "description": ["The mode in which the current VACUUM operation is running. See Section 24.1.5 for details of each mode. Possible values are:\n\nnormal: The operation is performing a standard vacuum. It is neither required to run in aggressive mode nor operating in failsafe mode. aggressive: The operation is running an aggressive vacuum, which must scan every page that is not marked all-frozen. The parameters vacuum_freeze_table_age and vacuum_multixact_freeze_table_age determine when a table requires aggressive vacuuming. failsafe: The vacuum has entered failsafe mode, in which it performs only the minimum work necessary to avoid transaction ID or multixact ID wraparound failure. The parameters vacuum_failsafe_age and vacuum_multixact_failsafe_age determine when the vacuum enters failsafe mode. The vacuum may start in this mode or switch to it while running; the value of the mode column may transition from another mode to failsafe during the operation."], "manual_html": "", "manual_path": "/docs/19/progress-reporting.html", "source_only": false, "comparison_data": {"view": "pg_stat_progress_vacuum", "field": "mode", "sql_type": "text", "units_mentioned": []}, "comparison_hash": "cbec24d7abf035a81604ce8ace972dd5a4bd3c343cf88ccd071b1eed01b09b4d", "units_mentioned": []}, "20": {"view": "pg_stat_progress_vacuum", "facts": [{"label": "View", "value": "pg_stat_progress_vacuum"}, {"label": "Field", "value": "mode"}, {"label": "SQL type", "value": "text"}, {"label": "Units named in the field definition", "value": "Not specified"}, {"label": "Reset observation", "value": "No stats_reset field is documented for this view"}], "field": "mode", "tables": [], "related": [{"url": "/wiki/catalog/pg_stat_progress_vacuum/?v=20", "label": "pg_stat_progress_vacuum columns"}, {"url": "/docs/devel/monitoring-stats.html", "label": "Statistics collection and reset functions"}], "release": {"ref": "https://ftp.postgresql.org/pub/snapshot/dev/postgresql-snapshot.tar.bz2", "label": "20devel", "major": "20", "channel": "devel", "revision": "4d3346909b201ac1648232cf290462a7070c119326f56196f1f0253ed80fae41"}, "sources": [{"url": "/docs/devel/progress-reporting.html#PG-STAT-PROGRESS-VACUUM-VIEW", "path": "progress-reporting.html", "label": "PostgreSQL 20 English manual", "sha256": "a692c859d24d77ff71231c72596243a279325b5436ece3dad58945b55688646e"}], "sections": [{"title": "View semantics", "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_repack, and is also visible via the backwards-compatibility 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.5 and Section 27.4.2."]}, {"title": "Collection and reset context", "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."]}, {"code": "SELECT mode FROM pg_catalog.pg_stat_progress_vacuum;", "title": "Inspect this field", "paragraphs": ["Example query; no execution result or measured value is asserted."]}], "sql_type": "text", "signature": "SELECT mode FROM pg_catalog.pg_stat_progress_vacuum;", "documented": true, "description": ["The mode in which the current VACUUM operation is running. See Section 24.1.5 for details of each mode. Possible values are:\n\nnormal: The operation is performing a standard vacuum. It is neither required to run in aggressive mode nor operating in failsafe mode. aggressive: The operation is running an aggressive vacuum, which must scan every page that is not marked all-frozen. The parameters vacuum_freeze_table_age and vacuum_multixact_freeze_table_age determine when a table requires aggressive vacuuming. failsafe: The vacuum has entered failsafe mode, in which it performs only the minimum work necessary to avoid transaction ID or multixact ID wraparound failure. The parameters vacuum_failsafe_age and vacuum_multixact_failsafe_age determine when the vacuum enters failsafe mode. The vacuum may start in this mode or switch to it while running; the value of the mode column may transition from another mode to failsafe during the operation."], "manual_html": "", "manual_path": "/docs/devel/progress-reporting.html", "source_only": false, "comparison_data": {"view": "pg_stat_progress_vacuum", "field": "mode", "sql_type": "text", "units_mentioned": []}, "comparison_hash": "cbec24d7abf035a81604ce8ace972dd5a4bd3c343cf88ccd071b1eed01b09b4d", "units_mentioned": []}}}, "snapshot": null, "comparison": {"left": "17", "right": "18", "status": "unchanged", "diff": ""}}