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-11-16 17:10:08
Message-ID: CAGRkXqTG=uKp2fE90UCi-2as7fKrpDwU+yZfORu6QrzHMOhOEQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Melanie,

Thanks for catching this. 0001 looks right to me, and committing it
first makes sense.

Just curious, I think the overflow could only happen in 32bit build, do
we still support it?

Thanks,
Shihao

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2026-11-16 17:53:35 Re: BUG #19899: PL/Python backend crashes (SIGSEGV) when converting a column value to a Python object fails
Previous Message Andres Freund 2026-11-16 16:29:07 Re: PG 18 JIT regression: int4range hash breaks multi-key GROUP BY