Re: Add PortalDrop in exec_execute_message

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Add PortalDrop in exec_execute_message
Date: 2021-06-07 22:15:49
Message-ID: 1029215.1623104149@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> On 2021-Jun-07, Alvaro Herrera wrote:
>> The attached patch does it. Any opinions?

> Eh, really attached.

No particular objection. I'm not sure this will behave quite the
same as simple-Query in error cases, but probably it's close enough.

I'm still wondering though why Yura is observing resources remaining
held by an executed-to-completion Portal. I think investigating that
might be more useful than tinkering with pipeline mode.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-06-07 22:28:22 logical decoding and replication of sequences
Previous Message Tom Lane 2021-06-07 22:10:58 Re: A modest proposal vis hierarchical queries: MINUS in the column list