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

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-07-01 00:12:48
Message-ID: CAApHDvoG2WT+9pCkNiBNh34e4Y6G6bwdNOG_6_v8rUD8b_uNKw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, 31 May 2024 at 19:05, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
> > 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.

Since we've now branched for v18, I've pushed this.

Thank you for the reviews.

David

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2024-07-01 02:49:14 Re: BUG #18526: 'UPDATE' inconsistency using index scan with 'NOT EXIST' after upgrading to PostgreSQL 16
Previous Message Francisco Olarte 2024-06-30 09:52:59 Re: LibPQ doesn't say host=* translates to localhost