From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: oli.sennhauser@fromdual.com
Subject: Server configuration shot overview
Date: Fri, 31 Jul 2026 09:38:35 +0000
Message-ID: <178549071520.2195443.221949298120586040@wrigleys.postgresql.org> (raw)
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?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, oli.sennhauser@fromdual.com
Subject: Re: Server configuration shot overview
In-Reply-To: <178549071520.2195443.221949298120586040@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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