Re: BUG #19905: loread() with length near INT_MAX: "invalid memory alloc request size" (int32 overflow)

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: hackerzheng666(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19905: loread() with length near INT_MAX: "invalid memory alloc request size" (int32 overflow)
Date: 2026-11-16 19:33:19
Message-ID: B6654D52-7188-4328-93CB-8DA63F74566A@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 16 Nov 2026, at 20:31, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> On 16 Nov 2026, at 19:37, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> (It's not just your time to
>>> commit this, it's that you're loading more work on the translators.)
>
>> I made sure to re-use an exsting error message from the large object code to
>> avoid translation work for no reason. Otherwise this would've been net-negative
>> for sure.
>
> Oh, okay. In that case I have no objection if you want to push this.
> But probably master-only (else I'm gonna have to write a release note)

Absolutely, this has no business in the backbranches.

--
Daniel Gustafsson

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2026-11-16 19:44:21 Re: BUG #19899: PL/Python backend crashes (SIGSEGV) when converting a column value to a Python object fails
Previous Message Tom Lane 2026-11-16 19:31:58 Re: BUG #19905: loread() with length near INT_MAX: "invalid memory alloc request size" (int32 overflow)