Horton

Re: Suggested fix for \p and \r in psql

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Daniel Verite" <daniel@manitou-mail.org>
Cc: pgsql-hackers@postgresql.org
Date: 2017-04-02T20:02:24Z
Lists: pgsql-hackers 
"Daniel Verite" <daniel@manitou-mail.org> writes:
> 	Tom Lane wrote:
>> If we do phrase it like that, I think that the most natural behavior
>> for \r is the way I have it in HEAD --- you'd expect it to clear
>> the query buffer, but you would not expect it to forget the most
>> recent command.

> Okay, leaving out \r as it is and changing only \p works for me.

Sold, I'll adjust your patch and push it.

			regards, tom lane

Commits

  1. Doc: clarify behavior of OT_WHOLE_LINE and OT_FILEPIPE psql slash commands.

  2. Document psql's behavior of recalling the previously executed query.

  3. Fix behavior of psql's \p to agree with \g, \w, etc.

  4. Support \if ... \elif ... \else ... \endif in psql scripting.