pgsql: Document psql's behavior of recalling the previously executed qu

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Document psql's behavior of recalling the previously executed qu
Date: 2017-04-02 23:02:01
Message-ID: E1cuoVV-0003HU-Si@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

Various psql slash commands that normally act on the current query buffer
will automatically recall and re-use the most recently executed SQL command
instead, if the current query buffer is empty. Although this behavior is
ancient (dating apparently to commit 77a472993), it was documented nowhere
in the psql reference page. For that matter, we'd never bothered to define
the concept of "current query buffer" explicitly. Fix that. Do some
wordsmithing on relevant command descriptions to improve clarity and
consistency.

Discussion: https://postgr.es/m/9b4ea968-753f-4b5f-b46c-d7d3bf7c8f90@manitou-mail.org

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/68dba97a4dea5c5c915e31978a475107c17c458d

Modified Files
--------------
doc/src/sgml/ref/psql-ref.sgml | 73 ++++++++++++++++++++++++++++++------------
1 file changed, 52 insertions(+), 21 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-04-02 23:19:21 pgsql: Remove reinvention of stringify macro.
Previous Message Tom Lane 2017-04-02 20:50:31 pgsql: Fix behavior of psql's \p to agree with \g, \w, etc.