Re: Eagerly scan all-visible pages to amortize aggressive vacuum - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: Eagerly scan all-visible pages to amortize aggressive vacuum
Date
Msg-id CAD21AoCe=+Ho=zQTaVW=D=J-eqecy225gEt=VB5h0LDS_U83Ow@mail.gmail.com
Whole thread Raw
In response to Re: Eagerly scan all-visible pages to amortize aggressive vacuum  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-hackers
On Wed, Jan 29, 2025 at 6:08 AM Melanie Plageman
<melanieplageman@gmail.com> wrote:
>
> On Tue, Jan 28, 2025 at 4:38 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> >
> >
> > Thank you for updating the patch! These updates look good to me.
>
> Thanks for taking another look!
>
> > BTW I realized that we need to update tab-complete.c too to support
> > the tab-completion for vacuum_max_eager_freeze_failure_rate.
>
> I'm pretty sure tab-complete.c is auto-generated now. Tab completion
> for vacuum_max_eager_freeze_failure_rate worked for me without doing
> anything extra.

I missed to mention; it's about the tab completion for
vacuum_max_easter_freeze_failure storage parameter. We still need to
update the tab-complete.in.c file (I mentioned the wrong file
previously) for that.

Regards,

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



pgsql-hackers by date:

Previous
From: Nitin Jadhav
Date:
Subject: Re: Back patch of Remove durable_rename_excl()
Next
From: Tom Lane
Date:
Subject: Re: Fwd: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?