On Sat, 2012-03-24 at 19:07 -0400, Tom Lane wrote:
Jeff Davis pg...@j-davis.com writes:
Surely we don't want it to be set from the environment, right?
Why not?
I agree that we shouldn't change the documented behavior of those GUCs.
But a SQL command like CREATE DATABASE being environment
Jeff Davis pg...@j-davis.com writes:
On Sat, 2012-03-24 at 19:07 -0400, Tom Lane wrote:
Jeff Davis pg...@j-davis.com writes:
Surely we don't want it to be set from the environment, right?
Why not?
I agree that we shouldn't change the documented behavior of those GUCs.
But a SQL command
The documentation says:
The specified null string is sent by COPY TO without adding any
backslashes; conversely, COPY FROM matches the input against the null
string before removing backslashes.
-- http://www.postgresql.org/docs/devel/static/sql-copy.html
Those seem inconsistent with the
Jeff Davis pg...@j-davis.com writes:
The documentation says:
The specified null string is sent by COPY TO without adding any
backslashes; conversely, COPY FROM matches the input against the null
string before removing backslashes.
-- http://www.postgresql.org/docs/devel/static/sql-copy.html
The following bug has been logged on the website:
Bug reference: 6556
Logged by: Kasper Sandberg
Email address: kont...@sandberg-consult.dk
PostgreSQL version: 9.1.3
Operating system: -
Description:
looking at
