Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning - Mailing list pgsql-bugs

From David Rowley
Subject Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning
Date
Msg-id CAApHDvoG2WT+9pCkNiBNh34e4Y6G6bwdNOG_6_v8rUD8b_uNKw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18484: "Cannot enlarge string buffer" during parallel execution of prepared statement/partitioning  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-bugs
On Fri, 31 May 2024 at 19:05, Daniel Gustafsson <daniel@yesql.se> wrote:
>
> > On 31 May 2024, at 03:25, Tom Lane <tgl@sss.pgh.pa.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



pgsql-bugs by date:

Previous
From: Francisco Olarte
Date:
Subject: Re: LibPQ doesn't say host=* translates to localhost
Next
From: Richard Guo
Date:
Subject: Re: BUG #18526: 'UPDATE' inconsistency using index scan with 'NOT EXIST' after upgrading to PostgreSQL 16