Horton
Menu

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

Álvaro Herrera <alvherre@kurilemu.de>

View thread
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2025-07-17T15:48:27Z
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)

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Minor cosmetic tweaks

  2. Simplify coding in ProcessQuery

  3. Remove assertion from PortalRunMulti

  4. Represent command completion tags as structs