Horton

Re: another autovacuum scheduling thread

David Rowley <dgrowleyml@gmail.com>

View thread
From: David Rowley <dgrowleyml@gmail.com>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Nathan Bossart <nathandbossart@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Jeremy Schneider <schneider@ardentperf.com>, Sami Imseih <samimseih@gmail.com>, pgsql-hackers@postgresql.org
Date: 2025-10-24T22:25:02Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add rudimentary table prioritization to autovacuum.

  2. Trigger more frequent autovacuums with relallfrozen

  3. Harden nbtree page deletion.

  4. Check for interrupts inside the nbtree page deletion code.

On Sat, 25 Oct 2025 at 10:14, Peter Geoghegan <pg@bowt.ie> wrote:
>
> On Wed, Oct 22, 2025 at 3:35 PM David Rowley <dgrowleyml@gmail.com> wrote:
> > If we had the varying sleep time as I mentioned above, the
> > failsafe code could even be removed as the
> > "autovacuum_vacuum_cost_delay / <tables score>" calculation would
> > effectively zero the sleep time with any table > failsafe age.
>
> I'm not sure what you mean by "the failsafe could be removed".
> Importantly, the failsafe will abandon all further index vacuuming.
> That's why it's presented as something that you as a user are not
> supposed to rely on.

I didn't realise it did that too. I thought it just dropped the delay
to zero. In that case, I revoke the statement.

David