Re: allow changing autovacuum_max_workers without restarting

Sami Imseih <simseih@amazon.com>

From: "Imseih (AWS), Sami" <simseih@amazon.com>

To: Nathan Bossart <nathandbossart@gmail.com>

Cc: Justin Pryzby <pryzby@telsasoft.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2024-05-03T12:57:18Z

Lists: pgsql-hackers

> That's true, but using a hard-coded limit means we no longer need to add a
> new GUC. Always allocating, say, 256 slots might require a few additional
> kilobytes of shared memory, most of which will go unused, but that seems
> unlikely to be a problem for the systems that will run Postgres v18.

I agree with this.


Regards,

Sami

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Give up on running with NetBSD/OpenBSD's default semaphore settings.
- 810a8b1c8051 18.0 landed
initdb: Do not report default autovacuum_worker_slots.
- 2b49492eda3f 18.0 landed
Lower default value of autovacuum_worker_slots in initdb as needed.
- 6d01541960e2 18.0 landed
Allow changing autovacuum_max_workers without restarting.
- c758119e5bfb 18.0 landed
Reserve a PGPROC slot and semaphore for the slotsync worker process.
- 2bdf1b2a2efc 18.0 cited
Make archiver process an auxiliary process.
- d75288fb27b8 14.0 cited
Correct the formulas for System V IPC parameters SEMMNI and SEMMNS in docs.
- 597f7e3a6ec3 9.6.0 cited