Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
От | Álvaro Herrera |
---|---|
Тема | Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti |
Дата | |
Msg-id | 202507171203.y6yp2n25fk6f@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
|
Список | 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
В списке pgsql-bugs по дате отправления: