Re: pgsql: Revert online data checksum transitions

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Masao Fujii <masao(dot)fujii(at)gmail(dot)com>
Subject: Re: pgsql: Revert online data checksum transitions
Date: 2026-09-16 12:43:15
Message-ID: C8AD0CF7-1B98-4AC2-B0F3-EC6702C81482@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

> On 16 Sep 2026, at 14:32, Aleksander Alekseev <aleksander(at)tigerdata(dot)com> wrote:

>>> We should remove data_page_checksum_version from the pg_control_checkpoint
>>> entry in pg_proc.dat and reduce proargmodes from 20 output columns to 19?
>>
>> Ugh, I thought I had tested everything but clearly missed this one. Will fix immediately when back from lunch.
>
> I noticed that the revert was applied to REL_19_STABLE but not the
> master branch. Just wanted to make sure that's the plan.

That's indeed the plan. The remaining issue that a user can, under the right
set of circumstances, get a false positive page verification in an orphaned
file failure during base backup. The warning is harmless for data integrity,
but is non-trivial for the user to resolve since we don't provide any tools for
dealing with orphaned files. Fixing this in master will reduce churn.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Manuel Reyes Bravo 2026-09-16 12:58:33 Re: pgsql: Revert online data checksum transitions
Previous Message Aleksander Alekseev 2026-09-16 12:32:07 Re: pgsql: Revert online data checksum transitions

Browse pgsql-hackers by date

  From Date Subject
Next Message Shinya Kato 2026-09-16 12:48:29 Re: Track skipped tables during autovacuum and autoanalyze
Previous Message Manuel Reyes Bravo 2026-09-16 12:42:03 Re: Distinguish publication exclusions in object addresses