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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, 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 22:34:00
Message-ID: CAApHDvoL6oM1rjuyAvh9VXn=szjQeMMyaCcgfyYgPc_CQjaMVQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, 31 May 2024 at 03:37, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> +1 for "(%zu bytes)", and also for not rounding off. This is a case
> where that won't make it more intelligible.

Here's a revised patch with "(%zu bytes)".

Unsure if this needs to wait until we branch or if it's fine to sneak
into v17. I'll leave it til after the branch unless anyone feels
differently.

David

Attachment Content-Type Size
adjust_enlargeStringInfo_error_msg_v2.patch application/octet-stream 906 bytes

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Japin Li 2024-05-31 01:12:29 Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
Previous Message Tobey, Paul SOPT 6151 2024-05-30 21:40:56 COPY FROM STDIN BINARY failure