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

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ã?lvaro Herrera <alvherre@kurilemu.de>, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2025-07-16T04:45:55Z
Lists: pgsql-bugs
On Tue, Jul 15, 2025 at 07:40:19PM -0400, Tom Lane wrote:
> Michael Paquier <michael@paquier.xyz> writes:
>> You mean as an extra assertion?  I am not sure that this is strongly
>> necessary but why not.
> 
> No, I meant that the comment could explain that if we fail to assign a
> non-unknown CMDTAG here, there's still a possibility of an outer
> Portal level supplying one.  But I don't see how to make a useful
> assertion about that.

Oh, OK, I was not sure about your point here.  Thanks for clarifying.
--
Michael

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