Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Subject: Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers
Date: 2026-10-06 16:43:47
Message-ID: CAD21AoDtup4xzK9sfipNOC61z4twGjBKs2k8NoOd4pA6HSAuWA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 5, 2026 at 9:10 AM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>
> On Sun, Oct 4, 2026 at 11:25 PM Michael Paquier <michael(at)paquier(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-10-06 16:51:46 Re: [PG19] eager aggregation gives wrong results because of bpchar_ops
Previous Message Alvaro Herrera 2026-10-06 16:39:25 Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes