From: Boris Kolpackov <boris@codesynthesis.com>
To: Alvaro Herrera <alvaro.herrera@2ndquadrant.com>
Cc: pgsql-hackers@lists.postgresql.org, Michael Paquier <michael@paquier.xyz>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Peter Geoghegan <pg@bowt.ie>
Subject: Re: Pipeline mode and PQpipelineSync()
Date: Thu, 8 Jul 2021 20:31:32 +0200
Message-ID: <boris.20210708201732@codesynthesis.com> (raw)
In-Reply-To: <202107081729.osyyji4ewzjk@alvherre.pgsql>
References: <boris.20210708165230@codesynthesis.com>
<202107081729.osyyji4ewzjk@alvherre.pgsql>
Alvaro Herrera <alvaro.herrera@2ndquadrant.com> writes:
> To be honest, I am hesitant to changing the charter in that way; I fear
> it may have consequences I don't foresee. I think the workaround is not
> *that* bad.
Ok, fair enough. I've updated my code to account for this and it seems
to be working fine now.
> I'm having a bit of trouble documenting this. I modified the paragraph in the
> pipeline mode docs to read:
>
> <para>
> <function>PQisBusy</function>, <function>PQconsumeInput</function>, etc
> operate as normal when processing pipeline results. Note that if no
> queries are pending receipt of the corresponding results,
> <function>PQisBusy</function> returns 0.
> </para>
How about the following for the second sentence:
"In particular, a call to <function>PQisBusy</function> in the middle
of a pipeline returns 0 if all the results for queries issued so far
have been consumed."
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: boris@codesynthesis.com, alvaro.herrera@2ndquadrant.com, michael@paquier.xyz, andrew@dunslane.net, pg@bowt.ie
Subject: Re: Pipeline mode and PQpipelineSync()
In-Reply-To: <boris.20210708201732@codesynthesis.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox