Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: michael(dot)banck(at)netapp(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning
Date: 2024-05-30 06:25:00
Message-ID: DFD0B0B3-DF21-4869-AAC9-96744487F767@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 30 May 2024, at 03:26, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:

> I think we should at least write a better error message. "out of
> memory" is misleading. I've attached a patch with some proposed better
> wording.
>
> The above will become:
> ERROR: string buffer exceeds maximum allowed length (1073741823)
> DETAIL: Cannot enlarge string buffer containing 1073741812 bytes by 32 more

Should we use a more human readable unit than bytes in the errmsg as well?

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Önder Kalacı 2024-05-30 07:15:10 Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
Previous Message David Rowley 2024-05-30 01:26:20 Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning