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

Поиск
Список
Период
Сортировка
От Andrew Garner
Тема Re: Protocol 3, Execute, maxrows to return, impact?
Дата
Msg-id f7b5dd6b0807281136q5a5a7eadwaad969c9ace97e92@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Protocol 3, Execute, maxrows to return, impact?  ("Stephen R. van den Berg" <srb@cuci.nl>)
Ответы Re: Protocol 3, Execute, maxrows to return, impact?  ("Francisco Figueiredo Jr." <francisco@npgsql.org>)
Список pgsql-hackers

On 7/27/08, Stephen R. van den Berg <srb@cuci.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.


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Stephen R. van den Berg"
Дата:
Сообщение: Re: Protocol 3, Execute, maxrows to return, impact?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: WITH RECUSIVE patches 0723