Re: Offline data checksum changes can cause incorrect checksum state on standbys

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Offline data checksum changes can cause incorrect checksum state on standbys
Date: 2026-08-31 23:31:42
Message-ID: CAN4CZFN5sOQvWTXr7Dm1J1HXwczikBfMjkbFQ7QmHsr+VHd5Mg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I found a case where the source's online enable occurs after divergence and was
> never seen by the target, but replay skips it instead of applying it:
> ....
> Maybe the watermark needs timeline context, or pg_rewind needs to adjust it
> when it comes from the target's divergent history?

Thanks! v8 adds the latter, with a new test case verifying this scenario.

Attachment Content-Type Size
v8-0002-pg_checksums-Refuse-interrupted-transitions-note-.patch application/octet-stream 7.7 KB
v8-0004-pg_combinebackup-Refuse-mixed-data-checksum-state.patch application/octet-stream 9.5 KB
v8-0005-doc-Explain-how-offline-and-online-checksum-chang.patch application/octet-stream 4.2 KB
v8-0001-Do-not-adopt-data-checksum-state-from-another-nod.patch application/octet-stream 128.5 KB
v8-0003-pg_rewind-Check-the-data-checksum-states-of-sourc.patch application/octet-stream 21.6 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-08-31 23:45:51 Re: Use pg_neg_s*_overflow() for open-coded negation overflow checks
Previous Message Zsolt Parragi 2026-08-31 23:18:36 Re: REPACK: warn about skipping foreign partitions