Re: pgsql: Online enabling and disabling of data checksums

From: Daniel Gustafsson <dgustafsson(at)postgresql(dot)org>
To: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Online enabling and disabling of data checksums
Date: 2026-04-06 14:57:43
Message-ID: 97C12A9C-D34F-42BA-936A-32C4E444B500@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

> On 6 Apr 2026, at 16:39, Aleksander Alekseev <aleksander(at)tigerdata(dot)com> wrote:
>
> Hi Daniel,
>
>> Online enabling and disabling of data checksums
>>
>> [...]
>
> I noticed a little mistake:

Thanks for looking!

> ```
> /*
> * Await state transition to "on" in all backends. When done we know that
> * data data checksums are both written and verified in all backends.
> */
> ```
>
> The word "data" is repeated twice.

Ugh.

> Also there are inconsistencies in the way
> XLogCtlData->data_checksum_version,
> ControlFileData->data_checksum_version and certain variables are
> assigned. Sometimes a hardcoded 0 is used and sometimes
> PG_DATA_CHECKSUM_OFF. I suggest using values of the enum
> ChecksumStateType for readability / consistency.

PG_DATA_CHECKSUM_OFF didn't exist until quite late in the lifetime of the
patch, and clearly not all uses of 0 were ported over.

> Here are corresponding patches.

I will take another look later today when I have more time, and commit them.

--
Daniel Gustafsson

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2026-04-06 15:19:13 pgsql: Expose helper functions scan_quoted_identifier and scan_identifi
Previous Message Robert Haas 2026-04-06 14:55:02 Re: pgsql: Reduce log level of some logical decoding messages from LOG to D