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 1whwm2-000VIz-2C for pgsql-docs@arkaria.postgresql.org; Thu, 09 Jul 2026 21:59:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1whwm0-00Erk5-2U for pgsql-docs@arkaria.postgresql.org; Thu, 09 Jul 2026 21:59:13 +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 1whwm0-00Erjw-1m for pgsql-docs@lists.postgresql.org; Thu, 09 Jul 2026 21:59:13 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1whwly-00000000NeR-2LKD for pgsql-docs@lists.postgresql.org; Thu, 09 Jul 2026 21:59:12 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id D8CBA63D342 for ; Thu, 09 Jul 2026 23:59:07 +0200 (CEST) Received: from s979.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id C077463D645; Thu, 09 Jul 2026 23:59:07 +0200 (CEST) Received: from localhost (unknown [172.22.191.6]) by s979.loopia.se (Postfix) with ESMTP id BF2A310BC384; Thu, 09 Jul 2026 23:59:07 +0200 (CEST) X-Virus-Scanned: amavis at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s474.loopia.se (amavis); dkim=pass (2048-bit key) header.d=yesql.se Received: from s934.loopia.se ([172.22.191.6]) by localhost (s474.loopia.se [172.22.190.14]) (amavis, port 10024) with LMTP id zT6h93qrfSHt; Thu, 9 Jul 2026 23:59:06 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.236 Received: from smtpclient.apple (customer-89-255-232-236.stosn.net [89.255.232.236]) (Authenticated sender: daniel@yesql.se) by s934.loopia.se (Postfix) with ESMTPSA id 9EEC6917F0A; Thu, 09 Jul 2026 23:59:05 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1783634345; bh=0eS4EDNiqwbKhNnvAEAmGUc94t4lK0gxPFt+frpuiO4=; h=From:Subject:Date:References:To:In-Reply-To; b=wGP11lyJ97YOGIAciqukc67nHbMaU/iIpkZXxkC15qj05nv3sva7BdRoQB8Rw/N1h h6/qmhb1auA0yfiNyKx7buBp6ZDLMNQymEXM2D+2UVVxwnUtmGUQwoZPP6Q3cP5CdZ kygp/cdavgBGSBCMg26iDwwmH3eL+ENKUHYNf6mo94yXn3KUEY8/rEZiVEtZDxVGD9 vzA32Zvf7N+fJ2zNG3HWTmBSQaO9poLn4ubJHE5/65V1ic90W7T7zt+EyXMKw51GJd 94o7ZbA1BUBlOoqJQY7HV0WePWxYZKLmDCW9HfZQSI4jH9SeI+mJf4Yisvcl6d+JVr S9XqkG5tyQ1Yg== From: Daniel Gustafsson Content-Type: multipart/mixed; boundary="Apple-Mail=_8E867BCA-0FC6-4968-B8D7-FBF9D6D86640" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.12\)) Subject: Re: 66.6. Database Page Layout Date: Thu, 9 Jul 2026 23:58:55 +0200 References: <178350739237.73862.4549076173872335741@wrigleys.postgresql.org> To: y.saburov@gmail.com, PostgreSQL-documentation In-Reply-To: <178350739237.73862.4549076173872335741@wrigleys.postgresql.org> Message-Id: <24B34848-3557-48E0-B601-A5BA4FC4E057@yesql.se> X-Mailer: Apple Mail (2.3776.700.51.11.12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail=_8E867BCA-0FC6-4968-B8D7-FBF9D6D86640 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 8 Jul 2026, at 12:43, PG Doc comments form = wrote: >=20 > The following documentation comment has been logged on the website: >=20 > Page: https://www.postgresql.org/docs/18/storage-page-layout.html > Description: >=20 >> The second field contains the page checksum if -k are enabled. >=20 > -k -- This is enabled by default; use --no-data-checksums to disable > checksums. >=20 > Why does this need to be clarified? I'm not entirely sure which part you are referring to, but I agree that = the current wording isn't very good. "The second field contains the page checksum if -k are enabled." I propose the attached patch which changes the sentence to "The second = field contains the page checksum if data checksums are enabled." with a link = to the Checksums chapter in the documentation instead. -- Daniel Gustafsson --Apple-Mail=_8E867BCA-0FC6-4968-B8D7-FBF9D6D86640 Content-Disposition: attachment; filename=page_layout_checksums.diff Content-Type: application/octet-stream; x-unix-mode=0644; name="page_layout_checksums.diff" Content-Transfer-Encoding: 7bit diff --git a/doc/src/sgml/storage.sgml b/doc/src/sgml/storage.sgml index 6b6377503bf..19924b98d71 100644 --- a/doc/src/sgml/storage.sgml +++ b/doc/src/sgml/storage.sgml @@ -797,7 +797,7 @@ data. Empty in ordinary tables. (PageHeaderData). Its format is detailed in . The first field tracks the most recent WAL entry related to this page. The second field contains - the page checksum if are + the page checksum if data checksums are enabled. Next is a 2-byte field containing flag bits. This is followed by three 2-byte integer fields (pd_lower, pd_upper, and --Apple-Mail=_8E867BCA-0FC6-4968-B8D7-FBF9D6D86640--