From: | <chrisnospam(at)1006(dot)org> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: selecting large result sets in psql using |
Date: | 2006-08-28 14:35:17 |
Message-ID: | 25649.193.206.186.101.1156775717.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.
I've just submitted an updated patch to pgsql-patches in a new
thread :)
Bye,
Chris.
--
Chris Mair
http://www.1006.org
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-08-28 14:44:36 | Re: [HACKERS] Performance testing of COPY (SELECT) TO |
Previous Message | chrisnospam | 2006-08-28 14:29:38 | updated patch for selecting large results sets in psql using cursors |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-08-28 14:44:36 | Re: [HACKERS] Performance testing of COPY (SELECT) TO |
Previous Message | chrisnospam | 2006-08-28 14:29:38 | updated patch for selecting large results sets in psql using cursors |