Re: [PATCHES] selecting large result sets in psql using

From: <chrisnospam(at)1006(dot)org>
To: <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <bruce(at)momjian(dot)us>, <david(at)fetter(dot)org>, <pgsql-hackers(at)postgresql(dot)org>, <peter_e(at)gmx(dot)net>
Subject: Re: [PATCHES] selecting large result sets in psql using
Date: 2006-08-23 16:38:50
Message-ID: 49392.87.6.213.195.1156351130.squirrel@www.endian.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

>> To cut the Gordon knot I'm going to suggest we use:
>
>> \set CURSOR_FETCH fetch_count
>
>> and \g and ; are modified such that when they see
>> this variable set to fetch_count > 0 and the buffer
>> is a select they would use the modified fetch/output code.
>
>> Does this sound reasonable to everyone?
>
> OK with me, but maybe call the variable FETCH_COUNT, to avoid the
> presupposition that the implementation uses a cursor. As I mentioned
> before, I expect we'll someday rework it to not use that.
>
> regards, tom lane

Ok,
sounds good.
I'm travelling this week, but can send an updated patch during the weekend.

Bye,
Chris.

--
Chris Mair
http://www.1006.org

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-08-23 16:54:21 Re: [PATCHES] COPY view
Previous Message Tom Lane 2006-08-23 16:34:46 Re: Tricky bugs in concurrent index build

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-08-23 16:54:21 Re: [PATCHES] COPY view
Previous Message Zoltan Boszormenyi 2006-08-23 16:15:04 Re: [HACKERS] COPY view