Message-ID: <680906dd.df0a0220.28565a.51ff@mx.google.com>
Sender: Michael Banck <mbanck@gmail.com>
Date: Wed, 23 Apr 2025 17:27:25 +0200
From: Michael Banck <mbanck@gmx.net>
To: Jeremy Schneider <schneider@ardentperf.com>
Cc: Ron Johnson <ronljohnsonjr@gmail.com>,
	"pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: Re: verify checksums online
References: <20250418141817.2457ac8d@ardentperf.com>
 <CANzqJaDJtXkDEsq3QFY6ywL2KwObAW-twWtZ0qJCsioH-75wWQ@mail.gmail.com>
 <20250418151826.11f54034@ardentperf.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20250418151826.11f54034@ardentperf.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://www.postgresql.org/message-id/680906dd.df0a0220.28565a.51ff%40mx.google.com>
Precedence: bulk

Hi,

On Fri, Apr 18, 2025 at 03:18:26PM -0700, Jeremy Schneider wrote:
> On Fri, 18 Apr 2025 17:32:19 -0400
> Ron Johnson <ronljohnsonjr@gmail.com> wrote:
> 
> > On Fri, Apr 18, 2025 at 5:18 PM Jeremy Schneider
> > <schneider@ardentperf.com> wrote:
> > 
> > > i think there had been some mailing list discussions years ago? the
> > > pg_checksum utility in core still can't do an online check right?
> > 
> > https://www.postgresql.org/docs/17/app-pgchecksums.html
> > 
> > "The server must be shut down cleanly before running pg_checksums."
> 
> Yes I read the docs. This utility has evolved over time including a
> complete rename, and I was just doublechecking here that we didn't miss
> a doc update in case this sentence applied to enable/disable but not to
> verify. As I said I'm assuming it's all accurate but just doing the
> paranoid double-check

I proposed a patch some years ago but it was rejected or at least not
accepted without major changes[1]. There is an external version of
pg_checksums which can do online checksums verification here (using the
above patch): https://github.com/credativ/pg_checksums


Michael

[1] https://commitfest.postgresql.org/patch/1733/