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 12:03:11
Message-ID: 202507171203.y6yp2n25fk6f@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dilip Kumar 2025-07-17 12:06:55 Re: BUG #18990: The results of equivalent queries are inconsistent (one returns 0, another returns -0)
Previous Message PG Bug reporting form 2025-07-17 11:30:40 BUG #18990: The results of equivalent queries are inconsistent (one returns 0, another returns -0)