Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Rahul <rahul(at)rhyadav(dot)dev>
Cc: Kirill Reshke <reshkekirill(at)gmail(dot)com>, Nktpro <nktpro(at)gmail(dot)com>, Pgsql Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Melanie Plageman <melanieplageman(at)gmail(dot)com>
Subject: Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
Date: 2026-10-09 03:13:21
Message-ID: CAGRkXqQOxqf3f_jG930T7J5QGjp7AJDYKSFVWRYZhuTXhoFSgA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Rahul,

Thanks for checking. Here is v4, rebased on the current master.

The test is now 060_vm_clear_truncate.pl, on the back branches too.
No code changes.

0002 now has "Backpatch-through: 17". In the 17 and 18 files its
commit message names heap_xlog_visible(), as you pointed out.

Thanks,
Shihao

Attachment Content-Type Size
nocfbot-v4-REL_17_STABLE.patch application/octet-stream 10.3 KB
v4-0001-Read-visibility-map-pages-with-RBM_ZERO_ON_ERROR-.patch application/octet-stream 3.4 KB
v4-0002-Initialize-zeroed-VM-pages-in-VM-clear-redo.patch application/octet-stream 2.4 KB
nocfbot-v4-REL_18_STABLE.patch application/octet-stream 10.3 KB
nocfbot-v4-REL_19_STABLE.patch application/octet-stream 10.4 KB
v4-0003-Add-test-for-standby-restart-after-VM-truncation.patch application/octet-stream 4.7 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message shihao zhong 2026-10-09 03:30:12 Re: BUG #19735: `jsonb_object_agg_unique_strict` drops a JSONB `null` value as if it were SQL NULL
Previous Message Hayato Kuroda (Fujitsu) 2026-10-09 02:56:18 RE: Streaming decoding fails with "unexpected table_index_fetch_tuple call during logical decoding" when a relation has a TOASTed conbin (follow-up to BUG #18641)