Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wplcZ-001psl-2G for pgsql-docs@arkaria.postgresql.org; Fri, 31 Jul 2026 11:41:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wplcY-00Fsc4-20 for pgsql-docs@arkaria.postgresql.org; Fri, 31 Jul 2026 11:41:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wpjhq-00FIwC-37 for pgsql-docs@lists.postgresql.org; Fri, 31 Jul 2026 09:39:06 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wpjho-00000001DPy-3svI for pgsql-docs@lists.postgresql.org; Fri, 31 Jul 2026 09:39:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=CxybcKCbPiqcpsZisDqXI+OhSI7YYJQkXuBoS2U9EQo=; b=6hB+oSVZHPJ9vl8NwhS7x1c6Zu 99c0EXboFSP4rZFD1/66PxZarp9RMDlnqkphLyLMMfX2BrjSOeXVsUxHRJaQy+b13aSGBs7Bv4V+7 YAKK0spEZkbbpv93ZBdwImvBVC+0dx4TVG8fiFm3JIWhzmDhWd+ueNb5wliokO2GFKYcWs9VboFgf PUT0Dh71eBaMaZBp5MdusPGtbZ8s0YvLrWHUDvP22hMgNwVcSizMnqRQpkdQwl9vcYDgwiVwWNeQ4 quss2vEaeCXRYTE6ySrdEMVRz3zyZfw/c7Saq6cX2u7ItXRI9C0x8fNj9acl6WhZCdNQKD1e69Bqm 7rQfvrqA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wpjho-003myn-2F for pgsql-docs@lists.postgresql.org; Fri, 31 Jul 2026 09:39:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1wpjhn-00000009Ej0-0PYG for pgsql-docs@lists.postgresql.org; Fri, 31 Jul 2026 09:39:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Server configuration shot overview To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: oli.sennhauser@fromdual.com Reply-To: oli.sennhauser@fromdual.com, pgsql-docs@lists.postgresql.org Date: Fri, 31 Jul 2026 09:38:35 +0000 Message-ID: <178549071520.2195443.221949298120586040@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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-SYNCHRO= NOUS-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-SYNCHRO= NOUS-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-CHECKPO= INT-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?