From: Greg Stark <gsstark@mit.edu>
To: Martijn van Oosterhout <kleptog@svana.org>
Cc: Dave Page <dpage@vale-housing.co.uk>
Cc: pgsql-hackers@postgresql.org, Hiroshi Inoue <inoue@tpf.co.jp>
Subject: Re: Practical impediment to supporting multiple SSL libraries
Date: 13 Apr 2006 11:14:57 -0400
Message-ID: <87ek01ik26.fsf@stark.xeocode.com> (raw)
In-Reply-To: <20060413113405.GF7362@svana.org>
References: <E7F85A1B5FF8D44C8A1AF6885BC9A0E4011C9C98@ratbert.vale-housing.co.uk>
<20060413113405.GF7362@svana.org>
Martijn van Oosterhout <kleptog@svana.org> writes:
> On Thu, Apr 13, 2006 at 12:12:25PM +0100, Dave Page wrote:
> > > Ok. I'm not sure what this "double copying" you're referring
> > > to is,
> >
> > The libpq driver copies results out of the PGresult struct into the
> > internal QueryResult classes. With libpq out of the loop, data can go
> > straight from the wire into the QR.
>
> Hmm, the simplest improvement I can think of is one where you
> register a callback that libpq calls whenever it has received a new
> tuple.
That could be useful for applications but I think a driver really wants to
retain control of the flow of control. To make use of a callback it would have
to have an awkward dance of calling whatever function gives libpq license to
call the callback, having the callback stuff the data in a temporary space,
then checking for new data in the temporary space, and returning it to the
user.
--
greg
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: gsstark@mit.edu, kleptog@svana.org, dpage@vale-housing.co.uk, inoue@tpf.co.jp
Subject: Re: Practical impediment to supporting multiple SSL libraries
In-Reply-To: <87ek01ik26.fsf@stark.xeocode.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