Re: Add PortalDrop in exec_execute_message

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Add PortalDrop in exec_execute_message
Дата
Msg-id 4160143.1621621400@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Add PortalDrop in exec_execute_message  (Yura Sokolov <y.sokolov@postgrespro.ru>)
Ответы Re: Add PortalDrop in exec_execute_message  (Yura Sokolov <y.sokolov@postgrespro.ru>)
Список pgsql-hackers
Yura Sokolov <y.sokolov@postgrespro.ru> writes:
> I propose to add PortalDrop at the 'if (completed)' branch of
> exec_execute_message.

This violates our wire protocol specification, which
specifically says

    If successfully created, a named portal object lasts till the end of
    the current transaction, unless explicitly destroyed. An unnamed
    portal is destroyed at the end of the transaction, or as soon as the
    next Bind statement specifying the unnamed portal as destination is
    issued. (Note that a simple Query message also destroys the unnamed
    portal.)

I'm inclined to think that your complaint would be better handled
by having the client send a portal-close command, if it's not
going to do something else immediately.

            regards, tom lane



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

Предыдущее
От: Andrew Dunstan
Дата:
Сообщение: Re: compute_query_id and pg_stat_statements
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: compute_query_id and pg_stat_statements