|From:||Bruce Momjian <bruce(at)momjian(dot)us>|
|To:||Daniel Verite <daniel(at)manitou-mail(dot)org>|
|Cc:||Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Everaldo Canuto <everaldo(dot)canuto(at)gmail(dot)com>, Chapman Flack <chap(at)anastigmatix(dot)net>, Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: proposal: alternative psql commands quit and exit|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Thu, Feb 1, 2018 at 07:47:14AM -0500, Bruce Momjian wrote:
> > There's also the issue that, in general, communicating different hints
> > and advice depending on the host operating system is not ideal.
> > Because people ask "how do I do such and such in psql?",
> > they do not ask "how do I do such and such in psql in Windows?".
> Well, the exit/quit API is just for users to get things done quickly,
> for typing portability. I don't think it is something that has to have
> a consistent API.
I think the next big question is if/where we want to document this new
behavior. We don't mention 'help' in the psql manual page, but we do
display it in the startup banner:
$ psql test
--> Type "help" for help.
What do we want to do with 'exit' and 'quit'? Just leave them
undocumented as compatibility commands? If so, I should at least add a
C comment about this.
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
|Next Message||Thomas Munro||2018-02-02 04:11:17||Re: JIT compiling with LLVM v9.0|
|Previous Message||Amit Kapila||2018-02-02 02:48:14||Re: Wait for parallel workers to attach|