Re: [HACKERS] selecting large result sets in psql using

From: Chris Mair <chrisnospam(at)1006(dot)org>
To: Bruce Momjian <bruce(at)momjian(dot)us>
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:10:25
Message-ID: 1155834625.3948.51.camel@dell.home.lan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


> > > 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... :)

Bye, Chris.

--

Chris Mair
http://www.1006.org

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-08-17 17:11:15 Re: Autovacuum on by default?
Previous Message Magnus Hagander 2006-08-17 17:05:17 Re: BugTracker (Was: Re: 8.2 features status)

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-08-17 17:12:08 Re: [HACKERS] selecting large result sets in psql using
Previous Message Gregory Stark 2006-08-17 16:59:11 Re: pgsql-patches reply-to (was Re: [PATCHES] selecting