Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti - Mailing list pgsql-bugs

From Álvaro Herrera
Subject Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
Date
Msg-id 202507171548.vxoce4gnxrid@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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)



pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Next
From: Sajith Prabhakar Shetty
Date:
Subject: Re: Postgres: Queries are too slow after upgrading to PG17 from PG15