| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
| Cc: | 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: | 2024-05-07 16:06:05 |
| Message-ID: | 20240507160605.GA2523153@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 03, 2024 at 12:57:18PM +0000, Imseih (AWS), Sami wrote:
>> 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.
Here's what this might look like. I chose an upper limit of 1024, which
seems like it "ought to be enough for anybody," at least for now.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-allow-changing-autovacuum_max_workers-without-res.patch | text/x-diff | 17.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Jungwirth | 2024-05-07 16:43:58 | Re: PERIOD foreign key feature |
| Previous Message | David G. Johnston | 2024-05-07 15:23:52 | Re: PERIOD foreign key feature |