From: Daniel Gustafsson <daniel@yesql.se>
To: David Rowley <dgrowleyml@gmail.com>
Cc: michael.banck@netapp.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning
Date: Thu, 30 May 2024 08:25:00 +0200
Message-ID: <DFD0B0B3-DF21-4869-AAC9-96744487F767@yesql.se> (raw)
In-Reply-To: <CAApHDvo+sBc1836ktwVNesgPb7L9Bx1=p4OQpeieq8pg0nW-hg@mail.gmail.com>
References: <18484-3e357ade5fe50e61@postgresql.org>
<CAApHDvo+sBc1836ktwVNesgPb7L9Bx1=p4OQpeieq8pg0nW-hg@mail.gmail.com>
> On 30 May 2024, at 03:26, David Rowley <dgrowleyml@gmail.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: daniel@yesql.se, dgrowleyml@gmail.com, michael.banck@netapp.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning
In-Reply-To: <DFD0B0B3-DF21-4869-AAC9-96744487F767@yesql.se>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox