Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
Date: 2025-07-17 15:48:27
Message-ID: 202507171548.vxoce4gnxrid@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2025-Jul-17, Tom Lane wrote:

> So rather than using the word "default", maybe like
>
> * If a command tag was requested and we did not fill in a
> * run-time-determined tag above, copy the parse-time tag
> * from the Portal. (There might not be any tag there either,
> * in edge cases such as empty prepared statements. That's OK.)

Oh yeah, this seems very clear. Pushed that way, thanks.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Oh, great altar of passive entertainment, bestow upon me thy discordant images
at such speed as to render linear thought impossible" (Calvin a la TV)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Sajith Prabhakar Shetty 2025-07-17 15:49:39 Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Previous Message Peter Geoghegan 2025-07-17 15:05:01 Re: Postgres: Queries are too slow after upgrading to PG17 from PG15