Re: [PATCHES] selecting large result sets in psql using
От | Bruce Momjian |
---|---|
Тема | Re: [PATCHES] selecting large result sets in psql using |
Дата | |
Msg-id | 200608171735.k7HHZDC27431@momjian.us обсуждение исходный текст |
Ответ на | Re: [PATCHES] selecting large result sets in psql using cursors (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [PATCHES] selecting large result sets in psql using
|
Список | pgsql-hackers |
Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > > Chris Mair wrote: > >> 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. 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. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-hackers по дате отправления: