> > >> 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.
> > That seems like it would be very awkward to use: you'd have to type
> > quite a bit to go from one mode to the other.
> > Personally I think that insisting on a one-letter command name is not
> > such a good idea if you can't pick a reasonably memorable name.
> > I'd suggest "\gc" (\g with a Cursor) or "\gb" (\g for a Big query)
> > or some such.
\gc sounds like a good idea to me :)
(I must admit gc reminds me about 'garbage collector', which in a weired
way is related with what we're doing here... At least more related than
'Great Britain' ;)
> So add it as a modifyer to \g? Yea, that works, but it doesn't work for
> ';' as a 'go' command, of course, which is perhaps OK.
Yes, it was intended to differentiate this command from ';';
In response to
pgsql-hackers by date
|Next:||From: Florian G. Pflug||Date: 2006-08-17 18:10:19|
|Subject: Re: An Idea for planner hints|
|Previous:||From: Matthew T. O'Connor||Date: 2006-08-17 17:47:37|
|Subject: Re: Autovacuum on by default?|
pgsql-patches by date
|Next:||From: Alvaro Herrera||Date: 2006-08-17 19:09:30|
|Subject: Re: Going for "all green" buildfarm results|
|Previous:||From: Bruce Momjian||Date: 2006-08-17 17:35:13|
|Subject: Re: [HACKERS] selecting large result sets in psql using|