From: | Boris Kolpackov <boris(at)codesynthesis(dot)com> |
---|---|
To: | Alvaro Herrera <alvaro(dot)herrera(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Pipeline mode and PQpipelineSync() |
Date: | 2021-06-24 09:06:42 |
Message-ID: | boris.20210624110032@codesynthesis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvaro(dot)herrera(at)2ndquadrant(dot)com> writes:
> Curious -- I just noticed that the server understands a message 'H' that
> requests a flush of the server buffer. However, libpq has no way to
> generate that message as far as I can see. I think you could use that
> to request results from the pipeline, without the sync point.
>
> I wonder if it's worth adding an entry point to libpq to allow access to
> this.
Yes, I think this can be useful. For example, an application may wish
to receive the result as soon as possible in case it's used as input
to some further computation.
> PQrequestFlush() or something like that ...
I think I would prefer PQflushResult() or something along these
lines ("request" is easy to misinterpret as "client request").
From | Date | Subject | |
---|---|---|---|
Next Message | Boris Kolpackov | 2021-06-24 09:10:41 | Re: Pipeline mode and PQpipelineSync() |
Previous Message | Peter Eisentraut | 2021-06-24 09:01:32 | Add tests for UNBOUNDED syntax ambiguity |