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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, 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 07:05:36
Message-ID: 4B8F1E5A-C0C8-4781-A6DA-18C1A0D0A4B6@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 31 May 2024, at 03:25, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> ..and it's changing translatable messages at a time when the translators don't need extra work.

This is a compelling argument for waiting for v18 I think.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Etsuro Fujita 2024-05-31 07:22:48 Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption
Previous Message Tom Lane 2024-05-31 01:25:45 Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning