| 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, Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: Pipeline mode and PQpipelineSync() |
| Date: | 2021-07-08 18:15:49 |
| Message-ID: | 202107081815.ne6nsoeox32x@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Looking at this again, I noticed that I could probably do away with the
switch on pipelineStatus, and just call pqPipelineProcessQueue in all
cases when appending commands to the queue; I *think* that will do the
right thing in all cases. *Except* that I don't know what will happen
if the program is in the middle of processing a result in single-row
mode, and then sends another query: that would wipe out the pending
results of the query being processed ... but maybe that problem can
already occur in some other way.
I'll have to write some more tests in libpq_pipeline to verify this.
--
Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/
"Java is clearly an example of money oriented programming" (A. Stepanov)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-07-08 18:17:41 | Re: Replace remaining castNode(…, lfirst(…)) and friends calls with l*_node() |
| Previous Message | David G. Johnston | 2021-07-08 18:03:27 | Re: enable_resultcache confusion |