| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allow changing autovacuum_max_workers without restarting |
| Date: | 2025-04-29 17:19:18 |
| Message-ID: | 1050120.1745947158@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(at)eisentraut(dot)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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-04-29 17:24:06 | Re: allow changing autovacuum_max_workers without restarting |
| Previous Message | Sami Imseih | 2025-04-29 17:14:45 | Re: Disallow redundant indexes |