| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org, "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-04-28 13:14:54 |
| Message-ID: | 713236.1745846094@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> This initdb output seems, well, kinda fake, which it is by its own
> admission.
Agreed.
> Could we do this less fake maybe like this:
> selecting default "max_connections", "autovacuum_worker_slots" ... 100, 16
> with the actual wait at the "..."?
Perhaps that would be all right ...
> (It doesn't seem impossible that someone will want to add more default
> selecting for various worker or process slots, and this would allow adding
> these easily, versus adding more "fake" output lines.)
... but I can't see this approach scaling to three or four or five
outputs. The line would get unreasonably long.
My own proposal given the way it works now is to just print
max_connections and not mention autovacuum_worker_slots at all.
Our choice for max_connections is worth reporting, but I don't
feel that everything derived from it needs to be reported.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Khan, Tanzeel | 2025-04-28 13:27:48 | Remove redundant comment regarding RelationBuildRowSecurity in relcache.c |
| Previous Message | vignesh C | 2025-04-28 12:56:56 | Re: Logical Replication of sequences |