| 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-23 00:34:32 |
| Message-ID: | 202106230034.w5e33heifbud@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-Jun-22, Alvaro Herrera wrote:
> > So I think it would be useful to clarify the server behavior and
> > specify it in the documentation.
>
> I'll see about improving the docs on these points.
So I started to modify the second paragraph to indicate that the client
would send data on PQflush/buffer full/PQpipelineSync, only to realize
that the first paragraph already explains this. So I'm not sure if any
changes are needed.
Maybe your complaint is only based on disagreement about what does libpq
do regarding queueing commands; and as far as I can tell in quick
experimentation with libpq, it works as the docs state already.
--
Álvaro Herrera Valdivia, Chile
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yugo NAGATA | 2021-06-23 00:36:58 | Re: Avoid stuck of pbgench due to skipped transactions |
| Previous Message | Yugo NAGATA | 2021-06-23 00:31:25 | Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors |