| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Nathan Bossart <nathandbossart(at)gmail(dot)com>, "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 22:36:17 |
| Message-ID: | 1353350.1736202977@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> How about trying the higher setting first in initdb? On any sane system that won't cost anything because it'll succeed with the higher value.
That might be a good compromise. You'd have to think about how
it should interact with initdb's probes for workable values of
max_connections. My first thought about that is to have initdb
set autovacuum_worker_slots to max_connections / 8 or thereabouts
as it works down the list of max_connections values to try. Or
you could do something more complicated, but I don't see a reason
to make it too complex.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-01-06 22:46:19 | Re: Alias of VALUES RTE in explain plan |
| Previous Message | Юрий Соколов | 2025-01-06 22:29:52 | Meson bug in detection of 64 atomics |