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

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

Hi Melanie,

> Jacky's original fix with XLogTruncateRelation() is the one I prefer.

Fine with me. I tested v5 on master, 19, 18 and 17. With the fix the
standby restarts.

One small thing. On 17 the test part does not apply, because
001_concurrent_transaction.pl has no standby there.

Thanks,
Shihao

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Sami Imseih 2026-10-14 02:02:47 Re: pg_stat_statements stores WITH HOLD cursor query with literals