Re: autovacuum: automatically propagate updated parameters - Mailing list pgsql-bugs

From Masahiko Sawada
Subject Re: autovacuum: automatically propagate updated parameters
Date
Msg-id CAD21AoD7sfwHoCuSvW3-wfpc4sBFxacz_TN0TENcygTqcmWyeg@mail.gmail.com
Whole thread
In response to Re: autovacuum: automatically propagate updated parameters  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-bugs
On Thu, Oct 1, 2026 at 12:11 AM Daniel Gustafsson <daniel@yesql.se> wrote:
>
> > On 1 Oct 2026, at 07:45, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> > On Wed, Sep 30, 2026 at 9:26 PM Bharath Rupireddy
> > <bharath.rupireddyforpostgres@gmail.com> wrote:
> >>
> >> On Wed, Sep 30, 2026 at 8:36 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> >>> That's very helpful for me. I'll monitor buildfarm animals as much as I can.
> >>
> >> Thanks Daniel, and thanks Sawada-san. I will also keep an eye on the BF animals.
> >
> > After more thought, I need to push another fix for the buildfarm
> > failure anyway, so I can take this patch too. Sorry for going back and
> > forth on this. I'll push the attached 0001 patch  tomorrow, barring
> > any objections.
>
> No worries at all, whatever works best for you.  Let me know if I can be of
> assistance in any way while you're travelling.

Pushed. Thank you for all your support.

Regards,

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



pgsql-bugs by date:

Previous
From: Samuel Olaoye
Date:
Subject: Wrong results: hashed SubPlan referenced twice after OR-qual extraction reuses a stale hash table (13 to 19beta4)
Next
From: Vladimir Savin
Date:
Subject: Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows