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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Michael Paquier <michael@paquier.xyz>

Cc: Álvaro Herrera <alvherre@kurilemu.de>, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org

Date: 2025-07-15T04:59:26Z

Lists: pgsql-bugs

Michael Paquier <michael@paquier.xyz> writes:
> ... I am wondering if we should not just nuke the assertion at the end
> of PortalRunMulti() instead, relying on the same check done at the
> beginning of ProcessUtility().

Yeah, I was starting to think about that solution too.  Removing
code seems nicer than adding more.

CC'ing Alvaro as the original author...

			regards, tom lane

Commits

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

Minor cosmetic tweaks
- e76221bd95f0 19 (unreleased) landed
Simplify coding in ProcessQuery
- a27c40bfe8ab 19 (unreleased) landed
Remove assertion from PortalRunMulti
- e0d3f3cfb6f2 18.0 landed
- c2720ac6010a 15.14 landed
- b9a89682846f 14.19 landed
- b8926a5b4bb8 19 (unreleased) landed
- 4871c1e9cb6e 16.10 landed
- 43cd85962755 13.22 landed
- 0c466f5e0b34 17.6 landed
Represent command completion tags as structs
- 2f9661311b83 13.0 cited