BUG #14916: psql \r is invalid in PostgreSQL 10 - Mailing list pgsql-bugs

From David G. Johnston
Subject BUG #14916: psql \r is invalid in PostgreSQL 10
Date
Msg-id CAKFQuwbtFAxDdGJAS+qEfUxHPF1Qho+CHkiL7H_ir2ov4r5hQw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14916: psql \r is invalid in PostgreSQL 10  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #14916: psql \r is invalid in PostgreSQL 10  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Thursday, November 16, 2017, Tom Lane <tgl@sss.pgh.pa.us> wrote:
xyh@nvn.xyz writes:
> Hello,
> In PostgreSQL 10.0 and 10.1 .
> psql \r is invalid.

Please say why you think this is "invalid".  I'm pretty sure
it was an intentional behavioral change (associated with the
rewrite to support \if).  In any case it's not obviously worse
than before.  \r is supposed to clear the current query input
string; it says nothing about deleting history.


Actually, \r is behaving the same.  The behavior of \p has been changed (at least per the docs) to print the last executed query if the current buffer is empty.  This behavior change doesn't seem to be in the release notes.

David J.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #14916: psql \r is invalid in PostgreSQL 10
Next
From: Ashutosh Sharma
Date:
Subject: Re: 10.1: hash index size exploding on vacuum full analyze