| 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: Regression in pipeline mode in libpq 14.5 |
| Date: | 2022-08-15 15:24:37 |
| Message-ID: | 20220815152437.sg64tinuamfukbhz@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2022-Aug-14, Daniele Varrazzo wrote:
> The execute() runs an implicit BEGIN, which is also executed in
> pipeline mode. Exiting the pipeline() block causes a Sync. So we
> expect 3 results in the pipeline (a COMMAND_OK after BEGIN, a
> TUPLES_OK after SELECT, a PIPELINE_SYNC).
Hmm, it seems (judging only from comparing your two traces) that the
problem stems from the newly added hack to handle CloseComplete. I'll
have a look later in the week.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"No hay ausente sin culpa ni presente sin disculpa" (Prov. francés)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-08-15 15:54:01 | Re: [PATCH] Fix segfault calling PQflush on invalid connection |
| Previous Message | Daniele Varrazzo | 2022-08-15 14:57:58 | Re: [PATCH] Fix segfault calling PQflush on invalid connection |