Re: proposal: alternative psql commands quit and exit - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: proposal: alternative psql commands quit and exit
Date
Msg-id CAKFQuwbz-qmuGW0HH5n7oOm0tNLivGKJ3=+sb83WArv3n3A9vQ@mail.gmail.com
Whole thread Raw
In response to Re: proposal: alternative psql commands quit and exit  (Everaldo Canuto <everaldo.canuto@gmail.com>)
Responses Re: proposal: alternative psql commands quit and exit  (Ryan Murphy <ryanfmurphy@gmail.com>)
Re: proposal: alternative psql commands quit and exit  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Dec 8, 2017 at 7:26 AM, Everaldo Canuto <everaldo.canuto@gmail.com> wrote:
Didn't know about SHOW command. Are TABLES a reserved word?

​There isn't going to be that much appetite for this just so that people can use PostgreSQL without reading our documentation: or the output of typing "help" at the psql prompt that says "type \q to quit".​

I don't know how one would go about reasonably writing extensions for psql but that, to me, would be the preferred approach.  Then people could install whichever compatability module they'd like.

I'll agree that exiting the program is a special case that merits consideration - and it has been given that in the form of the concession to the word "help" in order to get the reader unfamiliar with our backslash prefix a non-backslash way to obtain that knowledge apart from reading our docs.  Under that premise I would accept (lacking compelling arguments for why its a bad idea) this proposal for quit/exit but am against anything beyond that.

David J.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: How to use set/reset role in contrib_regression test?
Next
From: Tom Lane
Date:
Subject: Re: Is it possible and worthy to optimize scanRTEForColumn()?