Re: allow changing autovacuum_max_workers without restarting - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: allow changing autovacuum_max_workers without restarting
Date
Msg-id aBELNrA_h4NKtTLi@nathan
Whole thread Raw
In response to Re: allow changing autovacuum_max_workers without restarting  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Apr 29, 2025 at 01:19:18PM -0400, Tom Lane wrote:
> Peter Eisentraut <peter@eisentraut.org> writes:
>> On 28.04.25 16:41, Nathan Bossart wrote:
>>> However, weren't we considering reverting some of this stuff [0]?  I see
>>> that sawshark is now choosing max_connections = 40 and
>>> autovacuum_worker_slots = 6, and since there are no other apparent related
>>> buildfarm failures, I'm assuming that nobody else is testing the 60
>>> semaphores case anymore.
>>> 
>>> [0] https://postgr.es/m/618497.1742347456%40sss.pgh.pa.us
> 
>> (I don't have any thoughts on this.)
> 
> Andres seemed lukewarm about reverting 38da05346 or 6d0154196, so
> I left it be for the moment.  But I still feel the argument is good
> that "these will do little except confuse future hackers".  Barring
> objection, I'll go revert them.

+1, I almost threatened the same but wasn't totally positive where the
discussion stood.

-- 
nathan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: allow changing autovacuum_max_workers without restarting
Next
From: Masahiko Sawada
Date:
Subject: Re: Slot's restart_lsn may point to removed WAL segment after hard restart unexpectedly