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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
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:31:58
Message-ID: 126619.1794857518@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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)

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Gustafsson 2026-11-16 19:33:19 Re: BUG #19905: loread() with length near INT_MAX: "invalid memory alloc request size" (int32 overflow)
Previous Message Tom Lane 2026-11-16 19:28:59 Re: BUG #19906: Backend crash (signal 11) creating a LANGUAGE sql function that returns a composite type from a sub-