Re: [PATCHES] selecting large result sets in psql using - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [PATCHES] selecting large result sets in psql using
Date
Msg-id 200608171712.k7HHC8E17082@momjian.us
Whole thread Raw
In response to Re: [PATCHES] selecting large result sets in psql using  (Chris Mair <chrisnospam@1006.org>)
List pgsql-hackers
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@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Enum proposal / design
Next
From: Kenneth Marshall
Date:
Subject: Re: BugTracker (Was: Re: 8.2 features status)