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

From Nathan Bossart
Subject Re: another autovacuum scheduling thread
Date
Msg-id acRROBvlokDLQZlh@nathan
Whole thread Raw
In response to Re: another autovacuum scheduling thread  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: another autovacuum scheduling thread
Re: another autovacuum scheduling thread
List pgsql-hackers
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.

-- 
nathan



pgsql-hackers by date:

Previous
From: SATYANARAYANA NARLAPURAM
Date:
Subject: LockHasWaiters() crashes on fast-path locks
Next
From: Bharath Rupireddy
Date:
Subject: Re: another autovacuum scheduling thread