Re: Pipeline mode and PQpipelineSync()

Alvaro Herrera <alvaro(dot)herrera(at)2ndquadrant(dot)com> writes:

> On 2021-Jul-08, Boris Kolpackov wrote:
>
> > Alvaro Herrera <alvaro(dot)herrera(at)2ndquadrant(dot)com> writes:
> >
> > > Hmm ... aren't you trying to read more results than you sent queries?
> >
> > Hm, but should I be able to? Or, to put another way, should PQisBusy()
> > indicate there is a result available without me sending a query for it?
> > That sounds very counter-intuitive to me.
>
> That seems a fair complaint, but I think PQisBusy is doing the right
> thing per its charter. It is documented as "would PQgetResult block?"
> and it is returning correctly that PQgetResult would not block in that
> situation, because no queries are pending.

Well, that's one way to view it. But in this case one can say that
the entire pipeline is still "busy" since we haven't seen the
PQpipelineSync() call. So maybe we could change the charter only
for this special situation (that is, inside the pipeline)?

But I agree, it may not be worth the trouble and a note in the
documentation may be an acceptable "solution".

I am happy to go either way, just let me know what it will be. And
also if the latest patch to libpq that you have shared[1] is still
necessary.

[1] https://www.postgresql.org/message-id/202107061747.tlss7f2somqf%40alvherre.pgsql