pgsql: Correct stdin/stdout usage in COPY .. PROGRAM

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Correct stdin/stdout usage in COPY .. PROGRAM
Date: 2014-09-30 20:00:53
Message-ID: E1XZ3bR-0004A7-3A@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Correct stdin/stdout usage in COPY .. PROGRAM

The COPY documentation incorrectly stated, for the PROGRAM case,
that we read from stdin and wrote to stdout. Fix that, and improve
consistency by referring to the 'PostgreSQL' user instead of the
'postgres' user, as is done in the rest of the COPY documentation.

Pointed out by Peter van Dijk.

Back-patch to 9.3 where COPY .. PROGRAM was introduced.

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/9adda98c7738f5a8d4fdaa5a7a5bfb3f11c94899

Modified Files
--------------
doc/src/sgml/ref/copy.sgml | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2014-10-01 10:23:53 pgsql: Rename CACHE_LINE_SIZE to PG_CACHE_LINE_SIZE.
Previous Message Alvaro Herrera 2014-09-30 15:08:28 pgsql: Fix pg_dump's --if-exists for large objects