| 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 13:10:15 |
| Message-ID: | CAN4CZFMFcgfgJ99RYhax-T+YJH=CWLy6ZGANMxf77SrSirw3VQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Thanks! I did not look in details but it looks like that pg_upgrade --check against
> a running source cluster with checksums enabled will still fail (finding === 2 in
> [0], tested with the test shared in [1]).
Yes, I missed that in the previous version, v7 fixes it.
| Attachment | Content-Type | Size |
|---|---|---|
| v7-0005-doc-Explain-how-offline-and-online-checksum-chang.patch | application/octet-stream | 4.2 KB |
| v7-0002-pg_checksums-Refuse-interrupted-transitions-note-.patch | application/octet-stream | 7.7 KB |
| v7-0003-pg_rewind-Check-the-data-checksum-states-of-sourc.patch | application/octet-stream | 21.6 KB |
| v7-0004-pg_combinebackup-Refuse-mixed-data-checksum-state.patch | application/octet-stream | 9.5 KB |
| v7-0001-Do-not-adopt-data-checksum-state-from-another-nod.patch | application/octet-stream | 119.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2026-08-31 13:12:45 | Re: RFC: Logging plan of the running query |
| Previous Message | vignesh C | 2026-08-31 12:53:41 | Re: Proposal: Conflict log history table for Logical Replication |