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

From Imseih (AWS), Sami
Subject Re: allow changing autovacuum_max_workers without restarting
Date
Msg-id 2780DB08-DCA6-4E57-B823-303A0E7E17D7@amazon.com
Whole thread Raw
In response to Re: allow changing autovacuum_max_workers without restarting  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: allow changing autovacuum_max_workers without restarting
List 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


pgsql-hackers by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Reducing the log spam
Next
From: Robert Haas
Date:
Subject: Re: Support LIKE with nondeterministic collations