From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | Chapman Flack <chap(at)anastigmatix(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: proposal: alternative psql commands quit and exit |
Date: | 2017-12-12 05:58:20 |
Message-ID: | 30157.1513058300@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Craig Ringer <craig(at)2ndquadrant(dot)com> writes:
> I doubt I've ever written just "exit" or "quit" without indentation. I
> think if it requires them to be a bareword with no indentation, strictly
> ^(exit|quit)\n when isatty, then that's probably a safe and helpful choice.
FWIW, I think that the special behavior (whatever it winds up being
exactly) ought to trigger on an input line matching
[whitespace]*help[whitespace]*(;[whitespace]*)?
and similarly for exit/quit. I think that novices might have internalized
enough SQL syntax to think that they need to terminate the command with a
semicolon --- in fact, we regularly see examples in which seasoned users
think they need to terminate backslash commands with a semicolon, so
that's hardly far-fetched. And we might as well allow as much whitespace
as we can, because nobody but Guido Rossum thinks that having whitespace
be semantically significant is a good idea.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2017-12-12 05:59:28 | Re: Using ProcSignal to get memory context stats from a running backend |
Previous Message | Michael Paquier | 2017-12-12 05:35:24 | Re: [HACKERS] A design for amcheck heapam verification |