Re: another autovacuum scheduling thread

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Sami Imseih <samimseih(at)gmail(dot)com>, Robert Treat <rob(at)xzilla(dot)net>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: another autovacuum scheduling thread
Date: 2026-03-10 15:06:44
Message-ID: abAzhNqs5F8sJDdm@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 05, 2026 at 11:03:50AM -0600, Nathan Bossart wrote:
> My apologies for getting distracted from this work. It might be a v20 item
> at this point. I haven't addressed any feedback since the v8 patch, but I
> did some testing.

Here's an updated patch with new GUCs that control how much each component
contributes to the autovacuum score for a table. They default to 1.0, but
can be set anywhere from 0.0 to 1.0 (inclusive). In theory, setting all of
them to 0.0 should restore the original pg_class order prioritization that
we have today. I haven't added corresponding reloptions for these GUCs, as
I'm not convinced we need them, but I can add them if folks think they
would be useful.

--
nathan

Attachment Content-Type Size
v9-0001-autovacuum-scheduling-improvements.patch text/plain 24.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2026-03-10 15:12:16 Re: Change initdb default to the builtin collation provider
Previous Message Ilia Evdokimov 2026-03-10 14:55:57 Re: Hash-based MCV matching for large IN-lists