| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "oli(dot)sennhauser(at)fromdual(dot)com" <oli(dot)sennhauser(at)fromdual(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Server configuration shot overview |
| Date: | 2026-07-31 12:20:17 |
| Message-ID: | CAKFQuwaBKoiCdR1tTdi-iMZ4uY1kBXeNrADDpPCzuNg8z6J_Jg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Friday, July 31, 2026, PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/18/runtime-config.html
> Description:
>
> When reading the configuration parameters
> (https://www.postgresql.org/docs/current/runtime-config-wal.html) I found
> it
> difficult to find fast the (for me) relevant information: What is the
> default? When/how can it be changed? The information is/was always there
> but
> somehow hidden in the text...
>
> So I think it would be more convenient to have these informations
> summarized
> in the beginning?
>
> What are other thinking about? Is it worth to take the effort and if yes
> how
> should this be done? All the 400 settings at once (pouhh!) or section by
> section?
>
Leaning toward no, but if I were to do something like this I’d avoid manual
updates and instead derive it from the catalog data already in the source
tree.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brian Brennglass | 2026-07-31 13:20:35 | Fwd: [PATCH] doc: outline all planner nodes |
| Previous Message | PG Doc comments form | 2026-07-31 09:38:35 | Server configuration shot overview |