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 1wVFIl-001ogc-1N for pgsql-docs@arkaria.postgresql.org; Thu, 04 Jun 2026 21:08:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wVFIj-008mvq-1U for pgsql-docs@arkaria.postgresql.org; Thu, 04 Jun 2026 21:08:29 +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 1wVFIj-008mvi-0e for pgsql-docs@lists.postgresql.org; Thu, 04 Jun 2026 21:08:29 +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 1wVFIh-000000018DO-1cXV for pgsql-docs@lists.postgresql.org; Thu, 04 Jun 2026 21:08:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=kIwuqDX+7pkizYaK2ZK3PRqW8wxWnXSj9ioRjYMl9+8=; b=R7mFd TqIQSkShiZc3qqX2nFS9bdkNBoYcDliOtmwlYprB5qydRG0w3fjTQBMwuL1ihscSV++aSrjVMaQtQ dAjN2XhlUkegZdE/jN+wwhslUTfF5VRlhJpelaSXZafq+C70h0paVZa1HOQpv9uXVfRzhUM43ZAhA /91Unc4tCiFkvTqQUFd+yeUc1qSJjs8mEZc2q/Z/0auPoE+bx8LZDmSRL5MBNXaqntNRhCaE06Hgy mha42VFgjFig1a+IdioQ0PMEM9qO0ISIAfKJ9z8Hf1M+XUHJsAeo+2/t6SJPSrwlruQW9vS0os600 Jz1ch9cFG8iLuzJA2ZOjMKccmnTKw==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1wVFIg-00000006POC-0vXQ; Thu, 04 Jun 2026 17:08:26 -0400 Date: Thu, 4 Jun 2026 17:08:26 -0400 From: Bruce Momjian To: Daniel Gustafsson Cc: PostgreSQL-documentation Subject: Re: pg_checksums docs mentioning online functions Message-ID: References: <3E59EA84-E150-468A-A316-FC99A009D235@yesql.se> <39395CB7-5BC5-4A44-9F31-4EAE7DCAC8C1@yesql.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <39395CB7-5BC5-4A44-9F31-4EAE7DCAC8C1@yesql.se> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Jun 4, 2026 at 10:39:53PM +0200, Daniel Gustafsson wrote: > > 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? Looks good, just one suggestion: > + 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. ... pg_checksums will still process all relation files regardless of the progress of online checksum processing. ------------------------------- I think this idea is complex enough that we have to clearly state "online _checksum_ processing." -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.