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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
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-31 01:25:45
Message-ID: 4302.1717118745@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> 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.

While I'd not fight against committing now, I'd lean to waiting
for v18. It's not a bug fix, and it's changing translatable
messages at a time when the translators don't need extra work.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Gustafsson 2024-05-31 07:05:36 Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning
Previous Message Japin Li 2024-05-31 01:12:29 Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption