Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation - Mailing list pgsql-bugs

From shihao zhong
Subject Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation
Date
Msg-id CAGRkXqQOxqf3f_jG930T7J5QGjp7AJDYKSFVWRYZhuTXhoFSgA@mail.gmail.com
Whole thread
In response to Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation  (Rahul <rahul@rhyadav.dev>)
List 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

pgsql-bugs by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: 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)
Next
From: shihao zhong
Date:
Subject: Re: BUG #19735: `jsonb_object_agg_unique_strict` drops a JSONB `null` value as if it were SQL NULL