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 1wVDEB-001n19-3A for pgsql-docs@arkaria.postgresql.org; Thu, 04 Jun 2026 18:55:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wVDE9-008CMW-1d for pgsql-docs@arkaria.postgresql.org; Thu, 04 Jun 2026 18:55:37 +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 1wVDE9-008CMO-0u for pgsql-docs@lists.postgresql.org; Thu, 04 Jun 2026 18:55:37 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wVDE7-000000017Io-1Bv4 for pgsql-docs@lists.postgresql.org; Thu, 04 Jun 2026 18:55:36 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=Content-Type:MIME-Version:Message-ID:Subject:Cc:To:From:Date: Sender:Reply-To:Content-Transfer-Encoding:Content-ID:Content-Description: In-Reply-To:References; bh=e01mWoXocvk0Lt7XQDoh+L7PZZol2kIcPD1Lfs4iVdk=; b=Cd rtOQCHIJRPVwWl6lJB2+VHHzS2IpM14XGJ02S1v67QlxKOzf0rzWKLOwoFdEbYvIbbf34rCn12yWt uzDVsSmtnu0AuGzmZv7CnDYAXqYx8m2pYC/zLyVreYKPdxUbWQ16lRzZdNqwXdyvAjhZdboLAorUI Rwa4VL4vCXcCtG61S4tmQ7VIy/w5v9C6yX2o/zyKPHTh/lla/+wQwkZqAI989oooxHG4wNDd4yLiU 76tDHk2gP2z8ZK+8anPvMva7h+2nWGBiTv12Ra2NBOV1I5RZMSZ0MCPyqloyn3Gp598DA+ybKQwxe CUlDCczUqxEWDn9Ws4a2aBxnYAlp5PGQ==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1wVDE5-000000061Sh-2ADU; Thu, 04 Jun 2026 14:55:33 -0400 Date: Thu, 4 Jun 2026 14:55:33 -0400 From: Bruce Momjian To: PostgreSQL-documentation Cc: Daniel Gustafsson Subject: pg_checksums docs mentioning online functions Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Looking at the pg_checksums docs, it says: pg_checksums checks, enables or disables data checksums in a PostgreSQL cluster. The server must be shut down cleanly before running pg_checksums. Do we want to mention the new functions here that can change the checksum status without being shut down? -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.