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

From Bharath Rupireddy
Subject Re: another autovacuum scheduling thread
Date
Msg-id CALj2ACV0rBhD3aBW-NQs20=ByHkZqhAPzKED=c49y2M4G=3i5g@mail.gmail.com
Whole thread
In response to Re: another autovacuum scheduling thread  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
Hi,

On Wed, Mar 25, 2026 at 2:18 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
>
> On Wed, Mar 25, 2026 at 02:12:16PM -0700, Bharath Rupireddy wrote:
> > Would it make sense to recompute scores and re-sort the remaining
> > table list after each table is processed in do_autovacuum()'s main
> > loop - say, after a certain amount of time spent vacuuming the large
> > table(s)? This would catch the above scenarios. I see that the scores
> > per table are being calculated in relation_needs_vacanalyze, but they
> > are ignored in the recheck path (table_recheck_autovac ->
> > recheck_relation_needs_vacanalyze -> relation_needs_vacanalyze).
>
> I think this was discussed a bit upthread, and we decided to leave it out
> for now.  But things like reprioritization and automatic cost limit
> adjustments seem worth considering for v20.

+1. Thanks for the clarification.

--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: another autovacuum scheduling thread
Next
From: Matthias van de Meent
Date:
Subject: Re: SQL-level pg_datum_image_equal