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 <[email protected]> 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 [email protected] https://www.fromdual.com Twitter: fromdual
OpenPGP_0xB58CF11D3C9DDEA9.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
