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 1wVErJ-001oL1-0K for pgsql-docs@arkaria.postgresql.org; Thu, 04 Jun 2026 20:40:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wVErH-008hun-2m for pgsql-docs@arkaria.postgresql.org; Thu, 04 Jun 2026 20:40:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wVErH-008huc-23 for pgsql-docs@lists.postgresql.org; Thu, 04 Jun 2026 20:40:07 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wVErF-00000001Ik9-37ew for pgsql-docs@lists.postgresql.org; Thu, 04 Jun 2026 20:40:07 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 46B13609046 for ; Thu, 04 Jun 2026 22:40:04 +0200 (CEST) Received: from s899.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 2E063608C66; Thu, 04 Jun 2026 22:40:04 +0200 (CEST) Received: from localhost (unknown [172.22.191.6]) by s899.loopia.se (Postfix) with ESMTP id 2BFDE2C8BA46; Thu, 04 Jun 2026 22:40:04 +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: s473.loopia.se (amavis); dkim=pass (2048-bit key) header.d=yesql.se Received: from s980.loopia.se ([172.22.191.6]) by localhost (s473.loopia.se [172.22.190.13]) (amavis, port 10024) with LMTP id P-iZGxVqiVvR; Thu, 4 Jun 2026 22:40:03 +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 s980.loopia.se (Postfix) with ESMTPSA id B34D3220164B; Thu, 04 Jun 2026 22:40:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1780605603; bh=kmC4ciD1r36/4z+YQFvup0UwvfpIvLbKcvhaCIbeBhc=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=G5zFlr39gYD7HxB9GKOseAlsy+xESZeIN0u4rnjSrZsmbQWPE4PtqNZP+SIdEtF0z oCo3aWV3d2waEnuD0N8SD/0hG7SBXAW4X2ALIMjRtvRS7LkPESOyv4VwIL1AYtJYIJ 0vF99Ld7lHczRV85qM5nI8z9sNahEjJmr8t92BLccVgUh4gPd60ui5fHWdW9K7kSEb +RAHwUNVA5fXkQITibLaKN1u7a3GKUUg1TiYEOl4Y/QAhN+9XrSHiFPYshBxTNC0n9 UDgUydBi3cdPrt//yXF+T3Il0S7/zlVv1iSfITRfEUtPtYgc6Mv/iixnAjE/q8kyo+ puSaeYqz4RnTQ== From: Daniel Gustafsson Message-Id: <39395CB7-5BC5-4A44-9F31-4EAE7DCAC8C1@yesql.se> Content-Type: multipart/mixed; boundary="Apple-Mail=_ABF42708-A945-471B-AC38-082823D0B750" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.12\)) Subject: Re: pg_checksums docs mentioning online functions Date: Thu, 4 Jun 2026 22:39:53 +0200 In-Reply-To: Cc: PostgreSQL-documentation To: Bruce Momjian References: <3E59EA84-E150-468A-A316-FC99A009D235@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=_ABF42708-A945-471B-AC38-082823D0B750 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii > On 4 Jun 2026, at 22:12, Bruce Momjian wrote: > My big issue is that we explain the limitation of pg_checksums, but > don't point readers at the tool that doesn't have that offline > restriction. I think we need that explicitly mentioned, and at the top. How about something like the attached? -- Daniel Gustafsson --Apple-Mail=_ABF42708-A945-471B-AC38-082823D0B750 Content-Disposition: attachment; filename=pg_checksums_docs.diff Content-Type: application/octet-stream; x-unix-mode=0644; name="pg_checksums_docs.diff" Content-Transfer-Encoding: 7bit diff --git a/doc/src/sgml/ref/pg_checksums.sgml b/doc/src/sgml/ref/pg_checksums.sgml index 45890324075..d1048d43f11 100644 --- a/doc/src/sgml/ref/pg_checksums.sgml +++ b/doc/src/sgml/ref/pg_checksums.sgml @@ -38,17 +38,22 @@ PostgreSQL documentation pg_checksums checks, enables or disables data checksums in a PostgreSQL cluster. The server - must be shut down cleanly before running - pg_checksums. When verifying checksums, the exit + must be shut down cleanly before running pg_checksums. + Checksums can also be enabled while the cluster is running using + processing, see + for further details on the different approaches. + When verifying checksums, the exit status is zero if there are no checksum errors, and nonzero if at least one checksum failure is detected. When enabling or disabling checksums, the exit status is nonzero if the operation failed. - When enabling checksums, if checksums were in the process of being enabled - when the cluster was shut down, pg_checksums - will still process all relations regardless of the online processing. + When enabling checksums with pg_checksums, if + checksums were in the process of being enabled using + when the cluster was shut + down, pg_checksums will still process all relation + files regardless of progress of the online processing. diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index c32931edde3..646076f7e39 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -276,7 +276,7 @@ - + Online Enabling of Checksums --Apple-Mail=_ABF42708-A945-471B-AC38-082823D0B750--