Date: Tue, 10 Mar 2026 11:19:20 -0500
From: Nathan Bossart <nathandbossart@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: David Rowley <dgrowleyml@gmail.com>, Sami Imseih <samimseih@gmail.com>,
	Robert Treat <rob@xzilla.net>,
	Jeremy Schneider <schneider@ardentperf.com>,
	pgsql-hackers@postgresql.org
Subject: Re: another autovacuum scheduling thread
Message-ID: <abBEiOICOdbbhsEI@nathan>
References: 
 <CAApHDvqK=dUa35oZjG8kh+A-aPof2pfsNmb-WXTMVHduKpm6bQ@mail.gmail.com>
 <CA+TgmoYCLqE-1vX9uhryF7NhOAT0v6+RP8E303u6rRgpFUiWyg@mail.gmail.com>
 <CAApHDvqFyEdWyEDT7NCKcqEi2sdchhOsA-+yWv_Zk=dRek4kgg@mail.gmail.com>
 <CA+TgmoZE=-Pw=85u+eX6UpMdY02o1otEhQba0n2T78yVyV2N9g@mail.gmail.com>
 <CAA5RZ0vzu4vfRP0podGDCBOn-OaK9Qs-oyksER5OtzanacqMQw@mail.gmail.com>
 <CA+TgmoZ44jzFBB4zxoXrX6iMxv7TPzv5duPe44UPpoyBBDL48g@mail.gmail.com>
 <CAApHDvo97hqpZR+vgVVSLQsPhVCA=yEerAGn9wzB_67vjmu6cA@mail.gmail.com>
 <CA+TgmoaAgv5D6u+_4KKqQFGH1n+jsFZ1mFWh+CSGqDUtyBNsXg@mail.gmail.com>
 <aam3dmZcia95-vB6@nathan>
 <abAzhNqs5F8sJDdm@nathan>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="PKfIir+1hRIDMz7Z"
Content-Disposition: inline
In-Reply-To: <abAzhNqs5F8sJDdm@nathan>
Archived-At: <https://www.postgresql.org/message-id/abBEiOICOdbbhsEI%40nathan>
Precedence: bulk


--PKfIir+1hRIDMz7Z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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

--PKfIir+1hRIDMz7Z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment;
	filename=v10-0001-autovacuum-scheduling-improvements.patch