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-09-01 13:50:04
Message-ID: CAN4CZFNdfb-yFRW7Sh3FkZ3Qc91Lz-JDQN0b-070-6G35g5Ssg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks!

I applied these changes to v9 with some additional comment editing. I
also squashed 0005 into 0001 because it describes what's implemented
there, and I also tried to significantly reduce the commit message of
0001. Otherwise everything else is unchanged.

Attachment Content-Type Size
v9-0003-pg_rewind-Check-the-data-checksum-states-of-sourc.patch application/octet-stream 21.6 KB
v9-0001-Do-not-adopt-data-checksum-state-from-another-nod.patch application/octet-stream 127.9 KB
v9-0004-pg_combinebackup-Refuse-mixed-data-checksum-state.patch application/octet-stream 9.5 KB
v9-0002-pg_checksums-Refuse-interrupted-transitions-note-.patch application/octet-stream 7.7 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-09-01 13:56:01 Re: [PATCH] doc: clarify AS requirement when VALUES used in a FROM clause
Previous Message vignesh C 2026-09-01 13:43:42 Re: Logical replication row filter loses unchanged toasted columns