pset, NULL, and COPY-reporting - Mailing list pgsql-admin

From John Bell
Subject pset, NULL, and COPY-reporting
Date
Msg-id 006c01d09d6e$af1de600$0d59b200$@ornl.gov
Whole thread Raw
Responses Re: pset, NULL, and COPY-reporting  ("David G. Johnston" <david.g.johnston@gmail.com>)
List 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



pgsql-admin by date:

Previous
From: fahad basheer
Date:
Subject: PgPool Load Balancing
Next
From: "David G. Johnston"
Date:
Subject: Re: pset, NULL, and COPY-reporting