Message-ID: <9541545c-2154-4fb8-9365-b789b3e10bae@vondra.me>
Date: Mon, 9 Feb 2026 23:36:30 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Changing the state of data checksums in a running cluster
To: Michael Banck <mbanck@gmx.net>
Cc: Daniel Gustafsson <daniel@yesql.se>, Andres Freund <andres@anarazel.de>,
 Bernd Helmle <mailings@oopsware.de>, Michael Paquier <michael@paquier.xyz>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
References: <d9ea8a27-ed46-476f-8a6e-600147b13ff2@vondra.me>
 <3e67160c-3676-4419-b635-1fdb80dc128e@vondra.me>
 <67726BDA-2F21-4D93-B01F-FA68212ED6F0@yesql.se>
 <9CA2495B-2D6C-4308-97EF-A12CCCAA753E@yesql.se>
 <c33d8d86-47ad-4cee-9860-26b324d7306b@vondra.me>
 <477897AE-1314-4724-9694-0BABC4F4ABDA@yesql.se>
 <5mv5vtbqj2xm2wmevsi22smyn32jtznva3ya3daih3ixh3onex@s5fyab63xt3c>
 <2535E72D-5979-4F58-A2D3-2AA4AA335C20@yesql.se>
 <DEE0237A-D38C-477F-997C-3B0EB2D4FC57@yesql.se>
 <775fddbc-4dec-413d-89bb-1a8186858ee6@vondra.me>
 <20260209075210.GB23161@p46.dedyn.io;lightning.p46.dedyn.io>
Content-Language: en-US
From: Tomas Vondra <tomas@vondra.me>
In-Reply-To: <20260209075210.GB23161@p46.dedyn.io;lightning.p46.dedyn.io>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/9541545c-2154-4fb8-9365-b789b3e10bae%40vondra.me>
Precedence: bulk

On 2/9/26 08:52, Michael Banck wrote:
> 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.
> 

What would that tell us? Let's say we force running pg_checksums even
after unclean shutdown and it reports some invalid page checksums - then
what? We don't know if that's a bug in the online checksums, or just
(expected) corruption due to immediate shutdown.


regards

-- 
Tomas Vondra