pset, NULL, and COPY-reporting

From: "John Bell" <jzb(at)ornl(dot)gov>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: pset, NULL, and COPY-reporting
Date: 2015-06-02 19:59:50
Message-ID: 006c01d09d6e$af1de600$0d59b200$@ornl.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Greetings --

Due to some level of ignorance at install-time, our "psql" clients on two
different production computers appear to have different values for /null/: ""
and "NULL" respectively.
At the same time, one of these computers reports the number of rows read-in with
a "\copy TABLE FROM FILE" command as "COPY 123", while the other computer does
not.

Is there some reference that tells specifically where the "default at login"
value of /null/ is set?
Is there some reference that tells what controls the "COPY 123" behavior?
Are the /null/ and COPY behaviors linked? If so, how?

Thank you for your consideration,
John Bell
ARM Archive
Oak Ridge National Lab

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message fahad basheer 2015-06-03 06:28:24 PgPool Load Balancing
Previous Message Guo, Yun 2015-06-02 15:03:15 Re: pg_dump not dumping some schemas