public inbox for [email protected]  

help / color / mirror / Atom feed

From: Michael Banck <[email protected]>
To: Tomas Vondra <[email protected]>
Cc: Daniel Gustafsson <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: Bernd Helmle <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Changing the state of data checksums in a running cluster
Date: Mon, 9 Feb 2026 08:52:10 +0100
Message-ID: <[email protected];lightning.p46.dedyn.io> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<5mv5vtbqj2xm2wmevsi22smyn32jtznva3ya3daih3ixh3onex@s5fyab63xt3c>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Hi,

On Fri, Feb 06, 2026 at 12:15:27AM +0100, Tomas Vondra wrote:
> It's a bit unfortunate we only detect invalid checksums if the failures
> appear in the server log. I wonder if we could run pg_checksums after
> the cluster gets shut down in 'fast' mode (we can't do that with
> immediate shutdowns, of course).

Well, maybe we could do that with immediate shutdowns if we add a
--force parameter to pg_checksums that is clearly labelled/docmented as
being dangerous for running instances (but the instance wouldn't run in
this case).  Or something undocumented like
--debug-force-unclean-controlfile.


Michael

view thread (60+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Changing the state of data checksums in a running cluster
  In-Reply-To: <[email protected];lightning.p46.dedyn.io>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox