diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-04-02 18:26:37 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-04-02 18:26:37 -0400 |
| commit | 68dba97a4dea5c5c915e31978a475107c17c458d (patch) | |
| tree | 3fb12207e9e8659e8b599844f7b8c3fdd74f633b /contrib/postgres_fdw/postgres_fdw.c | |
| parent | 5dbc5da1187c1ddb6e091047194d364337ebf232 (diff) | |
| download | postgresql-68dba97a4dea5c5c915e31978a475107c17c458d.tar.gz postgresql-68dba97a4dea5c5c915e31978a475107c17c458d.zip | |
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
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions