Horton

Re: Eagerly scan all-visible pages to amortize aggressive vacuum

Melanie Plageman <melanieplageman@gmail.com>

View thread View on postgr.es
From: Melanie Plageman <melanieplageman@gmail.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Robert Treat <rob@xzilla.net>, Marcos Pegoraro <marcos@f10.com.br>, Alena Rybakina <a.rybakina@postgrespro.ru>, Andres Freund <andres@anarazel.de>, Nazir Bilal Yavuz <byavuz81@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>, Peter Geoghegan <pg@bowt.ie>
Date: 2025-01-29T19:12:52Z
Lists: pgsql-hackers

Attachments

On Wed, Jan 29, 2025 at 12:59 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> 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.

Ah, thanks! I didn't realize that reloptions had tab-complete (and
that it was not automatically generated). I've fixed it now. Thanks so
much.

I also went through and took another pass at cleaning up comments.

- Melanie

Commits

  1. pg_stat_statements: Add counters for generic and custom plans

  2. Remove leftover mentions of XLOG_HEAP2_FREEZE_PAGE records

  3. Rename LVRelState->frozen_pages