Re: another autovacuum scheduling thread - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: another autovacuum scheduling thread
Date
Msg-id abBEiOICOdbbhsEI@nathan
Whole thread Raw
In response to Re: another autovacuum scheduling thread  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: another autovacuum scheduling thread
List pgsql-hackers
On Tue, Mar 10, 2026 at 10:06:44AM -0500, Nathan Bossart wrote:
> 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.

Apologies for the noise.  cfbot alerted me to a missing #include.

I've been thinking about how we might eventually translate these scores
into automatic cost limit adjustments.  ISTM that might be a bit difficult
because the scores are basically boundless, so we'll need to get creative.
Unfortunately, I have no concrete ideas to propose at the moment, but
that's v20 (or later) material, anyway.

-- 
nathan

Attachment

pgsql-hackers by date:

Previous
From: Paul A Jungwirth
Date:
Subject: Re: SQL:2011 Application Time Update & Delete
Next
From: Nico Williams
Date:
Subject: Re: Potential security risk associated with function call