Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers
Date
Msg-id CAD21AoBC+EGFwobZmuHDZKtMH72=EB1n8ehPASknaPs039-jqw@mail.gmail.com
Whole thread
In response to Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers  (Sami Imseih <samimseih.pg@gmail.com>)
Responses Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers
List pgsql-hackers
On Mon, Sep 28, 2026 at 2:34 PM Sami Imseih <samimseih.pg@gmail.com> wrote:
>
> Hi Bharath,
>
> Thanks for the feedback!
>
> > 1/ At the end of parallel_vacuum_main(), do we need to gate the
> > reporting of any remaining delay time on the accumulated delay time
> > variable rather than on the GUC?
>
> track_cost_delay_timing gates delay timing reporting elsewhere, so we should not
> deviate from that. If the GUC is off by then, we should not accumulate
> any timing
> anyhow, even if parallel_vacuum_worker_delay_ns > 0

IIUC the remaining parallel_vacuum_worker_delay_ns was accumulated
when the track_cost_delay_timing was enabled. Shouldn't we report it
as well?

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers
Next
From: jian he
Date:
Subject: Re: create table like including storage parameter