From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Chris Mair <chrisnospam(at)1006(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [HACKERS] selecting large result sets in psql using |
Date: | 2006-08-17 17:12:08 |
Message-ID: | 200608171712.k7HHC8E17082@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Chris Mair wrote:
>
> > > > BTW, \u seems not to have any mnemonic value whatsoever ... isn't there
> > > > some other name we could use?
> > >
> > > True :)
> > > Since buffer commands all have a single char I wanted a single char one
> > > too. The "c" for "cursor" was taken already, so i choose the "u" (second
> > > char in "cursor"). If somebody has a better suggestion, let us know ;)
> >
> > I think a new backslash variable isn't the way to go. I would use a
> > \pset variable to control what is happening.
>
> IMHO with \pset I'd have different places where I'd need to figure
> out whether to do the cursor thing and I was a bit reluctant to add
> stuff to existing code paths. Also the other \pset options are somewhat
> orthogonal to this one. Just my two EUR cents, of course... :)
Well, let's see what others say, but \pset seems _much_ more natural for
this type of thing to me.
--
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-17 17:13:58 | Re: Enum proposal / design |
Previous Message | Jim C. Nasby | 2006-08-17 17:11:45 | Re: Enum proposal / design |
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-08-17 17:21:19 | Re: Adjust autovacuum naptime automatically |
Previous Message | Chris Mair | 2006-08-17 17:10:25 | Re: [HACKERS] selecting large result sets in psql using |