Re: proposal: alternative psql commands quit and exit

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>
Cc: KAWAMICHI Ryoji <kawamichi(at)tkl(dot)iis(dot)u-tokyo(dot)ac(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: alternative psql commands quit and exit
Date: 2018-01-24 13:58:14
Message-ID: 20180124135814.rqaqq7gihjj65uqu@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Vik Fearing wrote:

> I haven't applied the patch, but what happens if you combine these?
> From your examples, I would imagine something like this:
>
> test=# select '
> test'# quit
> Use \q to quit or press control-C to clear the input buffer.
> test'# \q
> test'#
>
> Surely that's not helpful.

But there's a simple solution to that: make it two messages, one when
inside quotes ("Use Control-C to clear the input buffer, then \q to
quit") and one outside (current wording). Wasn't this already proposed
elsewhere in the thread?

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Geoff Winkless 2018-01-24 14:02:36 Re: proposal: alternative psql commands quit and exit
Previous Message Daniel Gustafsson 2018-01-24 13:50:30 Re: [HACKERS] Optional message to user when terminating/cancelling backend