Re: Changing the state of data checksums in a running cluster - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Changing the state of data checksums in a running cluster
Date
Msg-id 140B5D27-4A0D-42F4-966B-33B66734E594@yesql.se
Whole thread Raw
In response to Re: Changing the state of data checksums in a running cluster  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Changing the state of data checksums in a running cluster
List pgsql-hackers
> On 12 Mar 2026, at 00:56, Daniel Gustafsson <daniel@yesql.se> wrote:

One thing I forgot to mention was that this patch uncovered the same vmap (and
fsm) issue as is being discussed in [0].  At the time I didn't connect the dots
that it was an issue even without this patch so I tried to solve it as part of
this work.  After speaking with Andres I ripped out my attempts and will let
the other thread take care of the issue independently of this.

> * The change to XLOG_CHECKPOINT_REDO to move the wal_level into a proper record
>  structure should be pulled out as a 0001 patch as it's an cleanup that has
>  value on its own.

The attached rebase implements this by putting the XLOG_CHECKPOINT_REDO cleanup
as 0001.  This patch could (should?) be applied regardless of the fate of the
rest of the patchset.

--
Daniel Gustafsson

[0] CAAKRu_bn+e7F4yPFBgFbnP+syJRKyNK092bjD2LKvZW7O4Svag@mail.gmail.com


Attachment

pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Add missing stats_reset column to pg_statio_all_sequences view
Next
From: Andres Freund
Date:
Subject: Re: Why clearing the VM doesn't require registering vm buffer in wal record