From: Jeroen T. Vermeulen <jtv@xs4all.nl>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Client libraries supporting pipelining
Date: Tue, 14 Feb 2006 10:30:43 +0700 (ICT)
Message-ID: <14958.203.121.164.162.1139887843.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <8764njm0v9.fsf@mid.deneb.enyo.de>
References: <8764njm0v9.fsf@mid.deneb.enyo.de>
On Tue, February 14, 2006 03:59, Florian Weimer wrote:
> Which client libraries support pipelining, to reduce server
> round-trips?
The C++ interface libpqxx does support pipelining of queries--but perhaps
not quite at the level you had in mind.
Its "pipeline" class transparently batches up queries and lets you go off
to do useful stuff on the client side while they are being submitted and
processed. Thus it provides both "split-transaction" operation to hide
latency and batch submission to reduce the number of roundtrips. You get
to influence when the current batch is sent off, through a minimal
interface. Normal operation consists of inserting queries in the one end
and retrieving results out the other.
This is not an extremely sophisticated mechanism, however. It doesn't do
any client-side background processing, and it doesn't transparently
prepare statements before executing them. You could still prepare them
yourself, of course--or if it really helps to do so automatically, that
could be implemented under the existing API.
You can find libpqxx at http://thaiopensource.org/development/libpqxx/
Jeroen
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-interfaces@postgresql.org
Cc: jtv@xs4all.nl, fw@deneb.enyo.de
Subject: Re: Client libraries supporting pipelining
In-Reply-To: <14958.203.121.164.162.1139887843.squirrel@webmail.xs4all.nl>
* 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