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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
Дата
Msg-id 1400898.1752759934@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti  (Álvaro Herrera <alvherre@kurilemu.de>)
Ответы Re: BUG #18984: Empty prepared statement from psql \parse triggers assert in PortalRunMulti
Список pgsql-bugs
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de> writes:
> 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?], ..." ?

I think that where the Portal gets a tag is in PortalDefineQuery,
and that's normally set as a result of parsing.  The code earlier in
PortalRunMulti is meant to supply run-time-determined tags, such
as INSERT/UPDATE/DELETE with a row count.  I guess if you hold
your head at the right angle, the case we're considering now is
a run-time-determined tag for the outer EXECUTE.

            regards, tom lane



В списке pgsql-bugs по дате отправления: