Date: Fri, 18 Apr 2025 15:18:26 -0700
From: Jeremy Schneider <schneider@ardentperf.com>
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: Re: verify checksums online
Message-ID: <20250418151826.11f54034@ardentperf.com>
In-Reply-To: <CANzqJaDJtXkDEsq3QFY6ywL2KwObAW-twWtZ0qJCsioH-75wWQ@mail.gmail.com>
References: <20250418141817.2457ac8d@ardentperf.com>
	<CANzqJaDJtXkDEsq3QFY6ywL2KwObAW-twWtZ0qJCsioH-75wWQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/20250418151826.11f54034%40ardentperf.com>
Precedence: bulk

On Fri, 18 Apr 2025 17:32:19 -0400
Ron Johnson <ronljohnsonjr@gmail.com> wrote:

> On Fri, Apr 18, 2025 at 5:18=E2=80=AFPM Jeremy Schneider
> <schneider@ardentperf.com> wrote:
>=20
> > 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?
> >
>=20
> https://www.postgresql.org/docs/17/app-pgchecksums.html
>=20
> "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

-Jeremy