From: Craig Ringer <craig@2ndquadrant.com>
To: Heikki Linnakangas <hlinnakangas@vmware.com>
To: Matt Newell <newellm@blur.com>
To: pgsql-hackers@postgresql.org
Subject: Re: libpq pipelining
Date: Thu, 04 Dec 2014 22:30:46 +0800
Message-ID: <54807016.8010904@2ndquadrant.com> (raw)
In-Reply-To: <54802498.7020704@vmware.com>
References: <2059418.jZQvL3lH90@obsidian>
<54802498.7020704@vmware.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 12/04/2014 05:08 PM, Heikki Linnakangas wrote:
>>
>
> A good API is crucial for this. It should make it easy to write an
> application that does pipelining, and to handle all the error conditions
> in a predictable way. I'd suggest that you write the documentation
> first, before writing any code, so that we can discuss the API. It
> doesn't have to be in SGML format yet, a plain-text description of the
> API will do.
I strongly agree.
Applications need to be able to reliably predict what will happen if
there's an error in the middle of a pipeline.
Consideration of implicit transactions (autocommit), the whole pipeline
being one transaction, or multiple transactions is needed.
Apps need to be able to wait for the result of a query partway through a
pipeline, e.g. scheduling four queries, then waiting for the result of
the 2nd.
There are probably plenty of other wrinkly bits to think about.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: craig@2ndquadrant.com, hlinnakangas@vmware.com, newellm@blur.com
Subject: Re: libpq pipelining
In-Reply-To: <54807016.8010904@2ndquadrant.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