Try
Home   >   mailing lists

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

From Tom Lane
Subject Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
Date
Msg-id 1409149.1752764456@sss.pgh.pa.us
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>)
Responses Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
List pgsql-bugs
Tree view 
I wrote:
> =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de> writes:

> I think that where the Portal gets a tag is in PortalDefineQuery,
> and that's normally set as a result of parsing.

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.)

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18989: Output of \sf does not match original source for E quoted strings (unlike \df+ used to)
Next
From: Peter Geoghegan
Date:
Subject: Re: Postgres: Queries are too slow after upgrading to PG17 from PG15