| From: | Alvaro Herrera <alvaro(dot)herrera(at)2ndquadrant(dot)com> |
|---|---|
| To: | Boris Kolpackov <boris(at)codesynthesis(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Pipeline mode and PQpipelineSync() |
| Date: | 2021-06-25 23:50:10 |
| Message-ID: | 202106252350.t76x73nt643j@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-Jun-24, Boris Kolpackov wrote:
> Boris Kolpackov <boris(at)codesynthesis(dot)com> writes:
>
> > What's strange here is that the first PQgetResult() call (marked with ???)
> > returns NULL instead of result for INSERT #1 as in the first call sequence.
>
> I've hit another similar case except now an unexpected NULL result is
> returned in the middle of PGRES_PIPELINE_ABORTED result sequence. The
> call sequence is as follows:
I haven't been able to get this to break for me yet, and I probably
won't today. In the meantime, here's patches for the first one. The
test added by 0003 fails, and then 0004 fixes it.
--
Álvaro Herrera 39°49'30"S 73°17'W
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Clarify-that-pipeline-sync-is-mandatory.patch | text/x-diff | 1.4 KB |
| v2-0002-Add-PQrequestFlush.patch | text/x-diff | 3.3 KB |
| v2-0003-test-nosync.patch | text/x-diff | 3.4 KB |
| v2-0004-Fix-libpq-state-machine.patch | text/x-diff | 1.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-06-25 23:52:41 | Re: Pipeline mode and PQpipelineSync() |
| Previous Message | Jacob Champion | 2021-06-25 23:40:33 | Re: [PATCH] Pull general SASL framework out of SCRAM |