pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedServer configuration shot overview
3+ messages / 3 participants
[nested] [flat]
* Server configuration shot overview
@ 2026-07-31 09:38 PG Doc comments form <noreply@postgresql.org>
2026-07-31 12:20 ` Re: Server configuration shot overview David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: PG Doc comments form @ 2026-07-31 09:38 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: oli.sennhauser@fromdual.com
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?
3 Examples:
synchronous_commit (enum)
--------------|----------
Context | user
Default Value | on
Minimum Value | -
Maximum Value | -
Unit | -
Valid Values | remote_apply, on, remote_write, local, off
Specifies how much WAL processing must complete before...
https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT
---
full_page_writes (boolean)
--------------|----------
Context | sighup
Default Value | on
Minimum Value | -
Maximum Value | -
Unit | -
Valid Values | on, off
When this parameter is on, the PostgreSQL server...
https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-SYNCHRONOUS-COMMIT
---
checkpoint_timeout (integer)
--------------|----------
Context | sighup
Default Value | 300
Minimum Value | 30
Maximum Value | 86400
Unit | s
Valid Values | -
Maximum time between automatic WAL checkpoints...
https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-CHECKPOINT-TIMEOUT
---
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?
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Server configuration shot overview
2026-07-31 09:38 Server configuration shot overview PG Doc comments form <noreply@postgresql.org>
@ 2026-07-31 12:20 ` David G. Johnston <david.g.johnston@gmail.com>
2026-08-03 09:50 ` Re: Server configuration shot overview Oli Sennhauser <oli.sennhauser@fromdual.com>
0 siblings, 1 reply; 3+ messages in thread
From: David G. Johnston @ 2026-07-31 12:20 UTC (permalink / raw)
To: oli.sennhauser@fromdual.com <oli.sennhauser@fromdual.com>; pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
On Friday, July 31, 2026, PG Doc comments form <noreply@postgresql.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.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Server configuration shot overview
2026-07-31 09:38 Server configuration shot overview PG Doc comments form <noreply@postgresql.org>
2026-07-31 12:20 ` Re: Server configuration shot overview David G. Johnston <david.g.johnston@gmail.com>
@ 2026-08-03 09:50 ` Oli Sennhauser <oli.sennhauser@fromdual.com>
0 siblings, 0 replies; 3+ messages in thread
From: Oli Sennhauser @ 2026-08-03 09:50 UTC (permalink / raw)
To: David G. Johnston <david.g.johnston@gmail.com>; pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Deriving it from the catalog data IMHO is definitely the way to go. I
was not aware that this could be possible...
What are your arguments for leaning toward no? For other software
products I really like it.
Regards,
Oli
On 31/07/2026 14:20, David G. Johnston wrote:
> On Friday, July 31, 2026, PG Doc comments form
> <noreply@postgresql.org> wrote:
>
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/18/runtime-config.html
> <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
> <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.
>
--
FromDual - Neutral and vendor independent MariaDB, MySQL and PostgreSQL services.
FromDual GmbH Rebenweg 6
CH - 8610 Uster
Oli Sennhauser CEO / Senior Consultant
Phone: +41 44 500 58 20 Mobile: +41 79 830 09 33
oli.sennhauser@fromdual.com https://www.fromdual.com
Twitter: fromdual
Attachments:
[application/pgp-keys] OpenPGP_0xB58CF11D3C9DDEA9.asc (1.7K, ../../8eb2f15c-029c-4271-83e3-22c8f670357f@fromdual.com/3-OpenPGP_0xB58CF11D3C9DDEA9.asc)
download
[application/pgp-signature] OpenPGP_signature.asc (494B, ../../8eb2f15c-029c-4271-83e3-22c8f670357f@fromdual.com/4-OpenPGP_signature.asc)
download
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2026-08-03 09:50 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-07-31 09:38 Server configuration shot overview PG Doc comments form <noreply@postgresql.org>
2026-07-31 12:20 ` David G. Johnston <david.g.johnston@gmail.com>
2026-08-03 09:50 ` Oli Sennhauser <oli.sennhauser@fromdual.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox