From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>, Chris Mair <chrisnospam(at)1006(dot)org> |
Subject: | Re: [PATCHES] selecting large result sets in psql using |
Date: | 2006-08-19 04:52:43 |
Message-ID: | 200608190452.k7J4qhY08256@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
David Fetter wrote:
> 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.
True. They could even put it in .psqlrc if they want. Basically need a
way to modify \g. Seems a \set is the way we have always done such
modifications in the past. The big question is whether this is somehow
different. Personally, I don't think so.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-08-19 04:55:25 | Re: Windows 2000 Support |
Previous Message | Greg Sabino Mullane | 2006-08-19 03:03:46 | Re: Information_schema fixes for sequences and temporary tables |
From | Date | Subject | |
---|---|---|---|
Next Message | Dhanaraj M | 2006-08-19 08:22:24 | Re: Patch for - Change FETCH/MOVE to use int8 |
Previous Message | Greg Sabino Mullane | 2006-08-19 03:03:46 | Re: Information_schema fixes for sequences and temporary tables |