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 CAD21AoDtup4xzK9sfipNOC61z4twGjBKs2k8NoOd4pA6HSAuWA@mail.gmail.com
Whole thread
In response to Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Mon, Oct 5, 2026 at 9:10 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> On Sun, Oct 4, 2026 at 11:25 PM Michael Paquier <michael@paquier.xyz> wrote:
> >
> > On Tue, Sep 29, 2026 at 08:45:17AM -0700, Bharath Rupireddy wrote:
> > > Thanks. v3 path looks good to me.
> >
> > Yeah, reading through v3, that's not cool.  @Sawada-san, perhaps you
> > should look at that before v19 releases..
>
> Yes, the patch looks good to me too. I'm going to push it, barring objections.

Pushed.


Regards,

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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes
Next
From: Tom Lane
Date:
Subject: Re: [PG19] eager aggregation gives wrong results because of bpchar_ops