[COMMITTERS] pgsql: Fix pg_dump's --if-exists for large objects

2014-09-30 Thread Alvaro Herrera
Fix pg_dump's --if-exists for large objects This was born broken in 9067310cc5dd590e36c2c3219dbf3961d7c9f8cb. Per trouble report from Joachim Wieland. Pavel Stěhule and Álvaro Herrera Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/5f4f66f67184cc4696ffa3babc

[COMMITTERS] pgsql: Fix pg_dump's --if-exists for large objects

2014-09-30 Thread Alvaro Herrera
Fix pg_dump's --if-exists for large objects This was born broken in 9067310cc5dd590e36c2c3219dbf3961d7c9f8cb. Per trouble report from Joachim Wieland. Pavel Stěhule and Álvaro Herrera Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/fd02931a6c83bf3beb2d03f6570060078

[COMMITTERS] pgsql: Correct stdin/stdout usage in COPY .. PROGRAM

2014-09-30 Thread Stephen Frost
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 do

[COMMITTERS] pgsql: Correct stdin/stdout usage in COPY .. PROGRAM

2014-09-30 Thread Stephen Frost
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 do

[COMMITTERS] pgsql: Correct stdin/stdout usage in COPY .. PROGRAM

2014-09-30 Thread Stephen Frost
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 do