Re: allow changing autovacuum_max_workers without restarting

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, "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-01-06 21:29:37
Message-ID: 1346002.1736198977@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
> Committed.

Unsurprisingly, this has completely broken buildfarm member sawshark:
you added 13 new semaphores to the system's default requirements,
and we only had headroom for about 4 (cf. 38da05346).

Now maybe we should just abandon the notion that we ought to be
able to start up under OpenBSD/NetBSD's tiny default value of SEMMNS.
If so I'd be inclined to go revert 38da05346, at least in HEAD.
But I kind of wonder whether this feature actually brings value
commensurate with causing installation problems on real-world OSes.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2025-01-06 21:30:33 Re: A few patches to clarify snapshot management
Previous Message Robert Treat 2025-01-06 21:27:31 Re: Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN