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

PG Bug reporting form <noreply@postgresql.org> writes:
> The following psql script:
> \parse s

> execute s;

> invokes:
> TRAP: failed Assert("qc->commandTag != CMDTAG_UNKNOWN"), File: "pquery.c",
> Line: 1369, PID: 1123863

What this is complaining about, essentially, is that we don't know how
to construct a command tag to send back to the client.  Maybe we could
invent some new command tag out of whole cloth, but I'm inclined to
think it'd be better to forbid empty prepared statements.  Not sure
where that should be enforced, but probably on the server side.

            regards, tom lane