From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Everaldo Canuto <everaldo(dot)canuto(at)gmail(dot)com> |
Subject: | Re: proposal: alternative psql commands quit and exit |
Date: | 2018-01-07 00:40:54 |
Message-ID: | 151528565497.1766.3238531812004176940.pgcf@coridan.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I'm not sure what the usual shape of 'consensus' or 'resolution' is in these things,
but it seems to me that the branch of this email thread that leads here (through the
message from Robert that I'm replying to) is the one that felt like it was converging.
I thought it was converging on the idea that
^[whitespace]*(quit|exit)[whitespace]*(;[whitespace]*)?$
would be treated specially when interactive, whether on a first or a continuation line,
and that the special treatment would be a helpful explanatory message to the
interactive user, while nevertheless appending the text to the query buffer.
One possibly not-yet-converged point was whether the special treatment should
be the same on a first line, or should just actually quit in that case.
None of this is what the currently latest patch does, though.
-Chap
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2018-01-07 00:43:44 | Re: [HACKERS] GUC for cleanup indexes threshold. |
Previous Message | Tom Lane | 2018-01-07 00:38:03 | Re: [HACKERS] Refactoring identifier checks to consistently use strcmp |