| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>, Chris Mair <chrisnospam(at)1006(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: [PATCHES] selecting large result sets in psql using |
| Date: | 2006-08-18 17:16:40 |
| Message-ID: | 20060818171640.GC27614@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Fri, Aug 18, 2006 at 10:16:12AM -0400, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > A \set variable would make sense to me.
>
> So Peter and Bruce like a \set variable, Chris and I like a
> different command. Seems like a tie ... more votes out there
> anywhere?
It seems to me that a \set variable lets people use minimal
intrusiveness on scripts, etc., as they'll just set it when they start
needing cursor-ized result sets and unset it when finished.
Just my $.02 :)
Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Naz Gassiep | 2006-08-18 17:33:03 | Re: pg_dump schema breakup |
| Previous Message | Magnus Hagander | 2006-08-18 17:12:42 | Re: Windows 2000 Support |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-08-18 20:27:23 | Re: [PATCHES] plpython improvements |
| Previous Message | Tom Lane | 2006-08-18 14:16:12 | Re: [PATCHES] selecting large result sets in psql using |