Re: Changing the state of data checksums in a running cluster

From: Michael Banck <mbanck(at)gmx(dot)net>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, Andres Freund <andres(at)anarazel(dot)de>, Bernd Helmle <mailings(at)oopsware(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Changing the state of data checksums in a running cluster
Date: 2026-02-09 07:52:10
Message-ID: 20260209075210.GB23161@p46.dedyn.io;lightning.p46.dedyn.io
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-02-09 07:59:13 Re: Add expressions to pg_restore_extended_stats()
Previous Message Richard Guo 2026-02-09 07:43:40 Re: Convert NOT IN sublinks to anti-joins when safe