From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Shinoda, Noriyoshi (PN Japan A&PS Delivery)" <noriyoshi(dot)shinoda(at)hpe(dot)com> |
Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: psql small improvement patch |
Date: | 2019-12-07 17:58:12 |
Message-ID: | 31763.1575741492@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Shinoda, Noriyoshi (PN Japan A&PS Delivery)" <noriyoshi(dot)shinoda(at)hpe(dot)com> writes:
> I propose a small improvement to the psql command.
> Currently, psql's help/quit/exit command needs to start from the first position of the prompt.
> The attached patch allows the command to be executed ignoring leading white spaces.
Please read the (very long) thread in which this behavior was designed:
Allowing whitespace before the special command was part of the design
early on, eg my proposal at
https://www.postgresql.org/message-id/30157.1513058300%40sss.pgh.pa.us
but we eventually decided not to, see further down at
https://www.postgresql.org/message-id/20180125204630.GA27619%40momjian.us
If you want to reverse that decision you need to present cogent arguments
why, not just send in a patch.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-12-07 19:56:26 | Re: Windows buildfarm members vs. new async-notify isolation test |
Previous Message | Tom Lane | 2019-12-07 17:20:51 | Re: Windows buildfarm members vs. new async-notify isolation test |