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

From: Rahul <rahul(at)rhyadav(dot)dev>
To: shihao zhong <zhong950419(at)gmail(dot)com>
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-08 15:02:26
Message-ID: P3R1J53--F-9@rhyadav.dev
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Shihao,

cfbot says v3 needs a rebase.  0001 and 0002 still apply to master,
but the test's number is now taken: 12f866cd5f and cc33773482 added
058_shutdown_crash_restart.pl and 059_remote_apply_status_interval.pl
to src/test/recovery.  With the test renamed to
060_vm_clear_truncate.pl, the series applies to master (16b94c4012)
and the test passes.

As you were going to fold the heap_xlog_visible() wording for 17 and
18 into the next version, this may be a good time for v4.

Regards,
Rahul Yadav

Oct 3, 2026, 05:13 by zhong950419(at)gmail(dot)com:

> Hi Rahul,
>
> Thanks for testing v3 on all four branches.
>
> You are right about 17 and 18. I will change that sentence to
> heap_xlog_visible() in those two versions, and add
> "Backpatch-through: 17" to 0002. Both are commit message changes
> only, so I will fold them into the next version and not post a v4
> just for that.
>
> I added a CommitFest entry so this is tracked for the November
> releases.
>
> https://commitfest.postgresql.org/patch/7386/
>
> Thanks,
> Shihao
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Andrey Rachitskiy 2026-10-08 08:30:07 Re: PG18: use-after-free in exec partition pruning after an EPQ recheck in LockRows