| From: | Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Add PortalDrop in exec_execute_message |
| Date: | 2021-05-25 00:58:43 |
| Message-ID: | d5527cd4f9e9420b40b4947b375a7112@postgrespro.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane писал 2021-05-21 21:23:
> Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)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.
I thought about it as well. Then, if I understand correctly,
PQsendQueryGuts and PQsendQueryInternal in pipeline mode should send
"close portal" (CP) message after "execute" message, right?
regards,
Sokolov Yura
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-05-25 01:12:40 | Re: Test of a partition with an incomplete detach has a timing issue |
| Previous Message | Michael Paquier | 2021-05-25 00:46:58 | Re: Test of a partition with an incomplete detach has a timing issue |