{"Entry":{"collection":"metric","key":"pg_stat_progress_vacuum-delay_time","name":"pg_stat_progress_vacuum.delay_time","aliases":["delay_time","pg_stat_progress_vacuum"],"metadata":{"aliases":["delay_time","pg_stat_progress_vacuum"],"category":"pg_stat_progress_vacuum","content_hash":"1b7fc91ff723d61432ae902d2a20d82e46e86e93e5b363fb7cfd30f39e3bfe90","imported_at":"2026-09-30T00:40:45.965618+08:00","name":"pg_stat_progress_vacuum.delay_time","name_zh":"","slug":"pg_stat_progress_vacuum-delay_time","summary":"Total time spent sleeping due to cost-based delay (see Section 19.10.2), in milliseconds (if track_cost_delay_timing is enabled, otherwise zero). This includes the time that any associated parallel workers have slept. However, parallel workers report their sleep time no more frequently than once per second, so the reported value may be slightly stale."}},"Definition":{"Collection":"metric","Key":"pg_stat_progress_vacuum-delay_time","SourceDatabase":"center","Version":"18","SourceTable":"statistics_metric","SourceKey":"pg_stat_progress_vacuum-delay_time","SourceRevision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","Facts":{"comparison_data":{"field":"delay_time","sql_type":"double precision","units_mentioned":["milliseconds"],"view":"pg_stat_progress_vacuum"},"comparison_hash":"a867771974d827fb2050b817da26aeacb56a4900a8559fd6cc7bb7d7a442bb65","description":["Total time spent sleeping due to cost-based delay (see Section 19.10.2), in milliseconds (if track_cost_delay_timing is enabled, otherwise zero). This includes the time that any associated parallel workers have slept. However, parallel workers report their sleep time no more frequently than once per second, so the reported value may be slightly stale."],"documented":true,"facts":[{"label":"View","value":"pg_stat_progress_vacuum"},{"label":"Field","value":"delay_time"},{"label":"SQL type","value":"double precision"},{"label":"Units named in the field definition","value":"milliseconds"},{"label":"Reset observation","value":"No stats_reset field is documented for this view"}],"field":"delay_time","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 delay_time FROM pg_catalog.pg_stat_progress_vacuum;","paragraphs":["Example query; no execution result or measured value is asserted."],"title":"Inspect this field"}],"signature":"SELECT delay_time 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":"double precision","tables":[],"units_mentioned":["milliseconds"],"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-delay_time","SourceDatabase":"center","Version":"18","Locale":"en","Title":"pg_stat_progress_vacuum.delay_time","Summary":"Total time spent sleeping due to cost-based delay (see Section 19.10.2), in milliseconds (if track_cost_delay_timing is enabled, otherwise zero). This includes the time that any associated parallel workers have slept. However, parallel workers report their sleep time no more frequently than once per second, so the reported value may be slightly stale.","BodyHTML":"\u003cp\u003eTotal time spent sleeping due to cost-based delay (see Section 19.10.2), in milliseconds (if track_cost_delay_timing is enabled, otherwise zero). This includes the time that any associated parallel workers have slept. However, parallel workers report their sleep time no more frequently than once per second, so the reported value may be slightly stale.\u003c/p\u003e","SourceRevision":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","ContentHash":"a170986468171f10466958563802a8ef250ce87f73f8a894123357f260f97da5","Payload":{"description":["Total time spent sleeping due to cost-based delay (see Section 19.10.2), in milliseconds (if track_cost_delay_timing is enabled, otherwise zero). This includes the time that any associated parallel workers have slept. However, parallel workers report their sleep time no more frequently than once per second, so the reported value may be slightly stale."],"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 delay_time 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":["18","19","20"],"Locales":["en"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}