From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Samuel Williams <space(dot)ship(dot)traveller(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: libpq pipelineing |
Date: | 2020-06-27 06:32:09 |
Message-ID: | CAKFQuwYV7fx9iGNc5JDNnmEY7pOqXpqxgGx70_vvmBC0tJvfLw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Friday, June 26, 2020, Samuel Williams <space(dot)ship(dot)traveller(at)gmail(dot)com>
wrote:
> > What about, as it says, sending multiple statements in a single
> sendQuery and then polling for multiple results?
>
> I tried this, and even in single row streaming mode, I found that
> there are cases where the results would not be streamed until all the
> queries were sent.
>
> From the users point of view, they may generate a loop sending
> multiple queries and don't care about the result, so a pipeline/batch
> processing is ideal to avoid RTT per loop iteration, if database
> access is slow, this can be a significant source of latency
>
I don’t have any insight into the bigger picture but I’d concur that no
other option is documented so what you desire is not possible.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Samuel Williams | 2020-06-27 07:30:51 | Re: libpq pipelineing |
Previous Message | Samuel Williams | 2020-06-27 06:19:13 | Re: libpq pipelineing |