pgsql: Doc: clarify behavior of OT_WHOLE_LINE and OT_FILEPIPE psql slas

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Doc: clarify behavior of OT_WHOLE_LINE and OT_FILEPIPE psql slas
Date: 2017-04-02 23:02:01
Message-ID: E1cuoVV-0003HV-Sm@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

This is another bit of ancient behavior that was documented poorly (in
a couple of cases) or not at all (in several others).

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

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/ffac5998b4c18920f86d80f1bddbde9ebcf0a314

Modified Files
--------------
doc/src/sgml/ref/psql-ref.sgml | 88 +++++++++++++++++++++++++++++++++++++-----
1 file changed, 79 insertions(+), 9 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.