| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | chrisnospam(at)1006(dot)org |
| 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-22 22:33:35 |
| Message-ID: | 12409.1156286015@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
<chrisnospam(at)1006(dot)org> writes:
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2006-08-22 23:45:35 | Re: Tricky bugs in concurrent index build |
| Previous Message | Tom Lane | 2006-08-22 21:58:50 | Re: Where is hstore? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-08-23 02:45:54 | Re: [HACKERS] COPY view |
| Previous Message | chrisnospam | 2006-08-22 21:13:10 | Re: [PATCHES] selecting large result sets in psql using |