From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "xyh(at)nvn(dot)xyz" <xyh(at)nvn(dot)xyz>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | BUG #14916: psql \r is invalid in PostgreSQL 10 |
Date: | 2017-11-17 03:51:56 |
Message-ID: | CAKFQuwbtFAxDdGJAS+qEfUxHPF1Qho+CHkiL7H_ir2ov4r5hQw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thursday, November 16, 2017, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us
<javascript:_e(%7B%7D,'cvml','tgl(at)sss(dot)pgh(dot)pa(dot)us');>> wrote:
> xyh(at)nvn(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Sharma | 2017-11-17 06:20:57 | Re: 10.1: hash index size exploding on vacuum full analyze |
Previous Message | Tom Lane | 2017-11-17 03:43:07 | Re: BUG #14916: psql \r is invalid in PostgreSQL 10 |