Re: Protocol 3, Execute, maxrows to return, impact? - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: Protocol 3, Execute, maxrows to return, impact?
Date
Msg-id C5BF64E6-D6BD-4DA9-9A8F-952A4C7B6C22@fastcrypt.com
Whole thread Raw
In response to Re: Protocol 3, Execute, maxrows to return, impact?  ("Stephen R. van den Berg" <srb@cuci.nl>)
Responses Re: Protocol 3, Execute, maxrows to return, impact?  ("Stephen R. van den Berg" <srb@cuci.nl>)
List pgsql-hackers
On 27-Jul-08, at 3:00 PM, Stephen R. van den Berg wrote:

> Stephen R. van den Berg wrote:
>> My Pike drivers now support multiple simultaneous portals and
>> automatic streaming by presending overlapping Execute statements with
>> a dynamically adapted fetchlimit calculated per select as the query
>> progresses.
>
> They also support COPY now.
>
> The driver beats libpq in speed by about 62%.
> The memory consumption is on demand, by row, and not the whole  
> result set.
> Transport to and from the query is in binary and dynamically  
> determined
> per datatype, no quoting necessary.
>
> Anyone interested in taking a peek at the (GPL copyright) driver, I
> temporarily put up a small package which contains the working driver
> in Pike at:
>
>   http://admin.cuci.nl/psgsql.pike.tar.gz
>

This is very exciting news, I'd love to look at it, is there any way  
it could be re-licensed so that it can be incorporated into say the  
jdbc driver ?

Dave



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: issues/experience with building postgres on Windows
Next
From: "Marko Kreen"
Date:
Subject: Re: Do we really want to migrate plproxy and citext intoPG core distribution?