Request a Demo
Home   >   mailing lists

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

From Bharath Rupireddy
Subject Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers
Date
Msg-id CALj2ACUJpc+9TxGtuYR8q4bf0Nxj2CdvygehSuuJWvOEVZbOCA@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>)
List pgsql-hackers
Tree view 
Hi,

On Tue, Sep 29, 2026 at 6:48 AM Sami Imseih <samimseih.pg@gmail.com> wrote:
>
> > One nit, please feel free to ignore it. VacuumUpdateCosts() prints
> > yes/no for booleans, so on/off here could match that for consistency.
> > AFAICS, there is no hard rule, and I am fine with it as is.
>
> Better to be consistent here. Attached is v3-, which also updates the test
> output expected.

Thanks. v3 path looks good to me.

--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com

pgsql-hackers by date:

Previous
From: Anthonin Bonnefoy
Date:
Subject: Re: Protocol Compression (fourth attempt)
Next
From: Manu
Date:
Subject: Re: ATTACH PARTITION cost grows linearly with pg_constraint size (seqscan in CloneFkReferenced), much worse since not-null constraints are in pg_constraint (PG 18)