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

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: shihao zhong <zhong950419(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 18:13:18
Message-ID: CAAKRu_aT93e8wYNq9DkG7UoTLWYs1egtFCyNb9_y02uQtSC4UA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Nov 16, 2026 at 12:10 PM shihao zhong <zhong950419(at)gmail(dot)com> wrote:
>
> Just curious, I think the overflow could only happen in 32bit build, do
> we still support it?

You can see 32-bit animals on the buildfarm. Also, I think it's better
not to have this macro construct an intermediate value larger than the
input value.

- Melanie

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2026-11-16 18:37:42 Re: BUG #19905: loread() with length near INT_MAX: "invalid memory alloc request size" (int32 overflow)
Previous 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