{"kind": "metric", "major": "18", "item": {"slug": "pg_stat_progress_vacuum-started_by", "name": "pg_stat_progress_vacuum.started_by", "name_zh": "", "category": "pg_stat_progress_vacuum", "summary": "Not recorded in the selected version.", "aliases": ["started_by", "pg_stat_progress_vacuum"], "content_hash": "61795bea6c704dbffab890b7ddbc77b21c8a521d71b5377d93648ee2c1fe0d38", "versions": {"19": {"view": "pg_stat_progress_vacuum", "facts": [{"label": "View", "value": "pg_stat_progress_vacuum"}, {"label": "Field", "value": "started_by"}, {"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": "started_by", "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 started_by 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 started_by FROM pg_catalog.pg_stat_progress_vacuum;", "documented": true, "description": ["Shows what caused the current VACUUM operation to be started. Possible values are:\n\nmanual: The vacuum was started by an explicit VACUUM command. autovacuum: The vacuum was started by an autovacuum worker. Vacuums run by autovacuum workers may be interrupted due to lock conflicts. autovacuum_wraparound: The vacuum was started by an autovacuum worker to prevent transaction ID or multixact ID wraparound. Vacuums run for wraparound protection are not interrupted due to lock conflicts."], "manual_html": "", "manual_path": "/docs/19/progress-reporting.html", "source_only": false, "comparison_data": {"view": "pg_stat_progress_vacuum", "field": "started_by", "sql_type": "text", "units_mentioned": []}, "comparison_hash": "179de56f6743b02928d571be8741fdec140021d9b3f758168358dcd616283fbc", "units_mentioned": []}, "20": {"view": "pg_stat_progress_vacuum", "facts": [{"label": "View", "value": "pg_stat_progress_vacuum"}, {"label": "Field", "value": "started_by"}, {"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": "started_by", "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 started_by 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 started_by FROM pg_catalog.pg_stat_progress_vacuum;", "documented": true, "description": ["Shows what caused the current VACUUM operation to be started. Possible values are:\n\nmanual: The vacuum was started by an explicit VACUUM command. autovacuum: The vacuum was started by an autovacuum worker. Vacuums run by autovacuum workers may be interrupted due to lock conflicts. autovacuum_wraparound: The vacuum was started by an autovacuum worker to prevent transaction ID or multixact ID wraparound. Vacuums run for wraparound protection are not interrupted due to lock conflicts."], "manual_html": "", "manual_path": "/docs/devel/progress-reporting.html", "source_only": false, "comparison_data": {"view": "pg_stat_progress_vacuum", "field": "started_by", "sql_type": "text", "units_mentioned": []}, "comparison_hash": "179de56f6743b02928d571be8741fdec140021d9b3f758168358dcd616283fbc", "units_mentioned": []}}}, "snapshot": null, "comparison": {"left": "18", "right": "19", "status": "added", "diff": "--- PostgreSQL 18\n+++ PostgreSQL 19\n@@ -1 +1,6 @@\n-Not recorded in this version\n+{\n+  \"field\": \"started_by\",\n+  \"sql_type\": \"text\",\n+  \"units_mentioned\": [],\n+  \"view\": \"pg_stat_progress_vacuum\"\n+}"}}