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

From Nathan Bossart
Subject Re: another autovacuum scheduling thread
Date
Msg-id aROZpUyN1r24WyQ3@nathan
Whole thread Raw
In response to Re: another autovacuum scheduling thread  (Robert Treat <rob@xzilla.net>)
List pgsql-hackers
On Tue, Nov 11, 2025 at 02:50:55PM -0500, Robert Treat wrote:
> On Tue, Nov 11, 2025 at 2:49 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
>> On Tue, Nov 11, 2025 at 02:43:19PM -0500, Robert Treat wrote:
>> > FWIW, when I have built these types of systems in the past, and when I
>> > wanted an aggressive recheck-type mechanism, the most common methods
>> > involved tying it to autovacuum_max_workers.
>>
>> Would you mind elaborating on this point?  Do you mean that you'd rebuild
>> the list every a_m_w tables, or something else?
> 
> Yes.

Interesting.  With our defaults, that would mean rebuilding the list every
few tables, which seems quite aggressive.  I'd start worrying about the
pg_class scanning overhead a little...

-- 
nathan



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: another autovacuum scheduling thread
Next
From: Sami Imseih
Date:
Subject: Re: another autovacuum scheduling thread