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-17T12:03:11Z
Lists: pgsql-bugs 
On 2025-Jul-15, Tom Lane wrote:

> I might write the replacement comment more like
> 
>      * If query completion data is requested and not yet filled in,
>      * and the portal has a default command tag, copy it from there.
>      * See QueryRewrite(), step 3, for motivation.

I've been wondering what does the "a default command tag" mean there. 
I couldn't find a reference for a command tag being default.  Would it
work to say "... and the portal has acquired a command tag [during
execution above?], ..." ?

Thanks,

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Once again, thank you and all of the developers for your hard work on
PostgreSQL.  This is by far the most pleasant management experience of
any database I've worked on."                             (Dan Harris)
http://archives.postgresql.org/pgsql-performance/2006-04/msg00247.php

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