Re: Protocol 3, Execute, maxrows to return, impact?

From: "Andrew Garner" <andrew(dot)b(dot)garner(at)gmail(dot)com>
To: "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Protocol 3, Execute, maxrows to return, impact?
Date: 2008-07-28 18:36:13
Message-ID: f7b5dd6b0807281136q5a5a7eadwaad969c9ace97e92@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/27/08, Stephen R. van den Berg <srb(at)cuci(dot)nl> 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

I'd love to take a look at the code, but the link seems to be 404'd at the
moment.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-07-28 18:49:01 Re: WITH RECUSIVE patches 0723
Previous Message Stephen R. van den Berg 2008-07-28 18:29:42 Re: Protocol 3, Execute, maxrows to return, impact?