| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
| Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Using PQexecQuery in pipeline mode produces unexpected Close messages |
| Date: | 2022-06-08 15:08:47 |
| Message-ID: | 202206081508.pwq4ne3df2si@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 2022-Jun-08, Daniele Varrazzo wrote:
> Is this a problem with PQexecQuery which should not send the Close, or
> with receiving in IDLE mode which should expect a CloseComplete?
Interesting.
What that Close message is doing is closing the unnamed portal, which
is otherwise closed implicitly when the next one is opened. That's how
single-query mode works: if you run a single portal, it'll be kept open.
I believe that the right fix is to not send that Close message in
PQsendQuery.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Para tener más hay que desear menos"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-06-08 19:41:22 | BUG #17513: recompressing already-compressed data via VACUUM FULL or CLUSTER does not work |
| Previous Message | Christoph Berg | 2022-06-08 14:12:15 | Re: Fallout from 'Make type "name" collation-aware' and tg_table_name |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-06-08 15:54:34 | Re: invoker function security issues |
| Previous Message | Tomas Vondra | 2022-06-08 14:51:41 | Re: pgcon unconference / impact of block size on performance |