From: John Bell <jzb@ornl.gov>
To: pgsql-admin@postgresql.org
Subject: pset, NULL, and COPY-reporting
Date: Tue, 2 Jun 2015 15:59:50 -0400
Message-ID: <006c01d09d6e$af1de600$0d59b200$@ornl.gov> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jzb@ornl.gov
Subject: Re: pset, NULL, and COPY-reporting
In-Reply-To: <006c01d09d6e$af1de600$0d59b200$@ornl.gov>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox