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-09-22 17:31:02 |
Message-ID: | 20220922173102.axyflkz3w4gojhz7@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
So it'd be as in the attached.
In writing this, I also noticed that the extended query protocol
emulation I wrote for PQsendQuery had a bug, so the traces that result
by using PQsendQueryParams instead have a small difference.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"You don't solve a bad join with SELECT DISTINCT" #CupsOfFail
https://twitter.com/connor_mc_d/status/1431240081726115845
Attachment | Content-Type | Size |
---|---|---|
0001-remove-PQsendQuery-support-in-pipeline-mode.patch | text/x-diff | 16.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2022-09-22 18:47:06 | Re: PANIC in heap_delete during ALTER TABLE |
Previous Message | Dmitry Astapov | 2022-09-22 16:38:00 | Re: BUG #17619: AllocSizeIsValid violation in parallel hash join |