pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
pset, NULL, and COPY-reporting
3+ messages / 3 participants
[nested] [flat]

* pset, NULL, and COPY-reporting
@ 2015-06-02 19:59 John Bell <jzb@ornl.gov>
  2015-06-03 18:41 ` Re: pset, NULL, and COPY-reporting David G. Johnston <david.g.johnston@gmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: John Bell @ 2015-06-02 19:59 UTC (permalink / raw)
  To: 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



-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: pset, NULL, and COPY-reporting
  2015-06-02 19:59 pset, NULL, and COPY-reporting John Bell <jzb@ornl.gov>
@ 2015-06-03 18:41 ` David G. Johnston <david.g.johnston@gmail.com>
  2015-06-03 21:12   ` Re: pset, NULL, and COPY-reporting Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 3+ messages in thread

From: David G. Johnston @ 2015-06-03 18:41 UTC (permalink / raw)
  To: John Bell <jzb@ornl.gov>; +Cc: pgsql-admin

On Tuesday, June 2, 2015, John Bell <jzb@ornl.gov> wrote:

> 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?
>
>
Pretty sure the copy behavior is always on but version dependent.
You can decide what to have null output as using pset variables.  See the
documentation.  The default could have changed between versions, maybe...

David J.

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: pset, NULL, and COPY-reporting
  2015-06-02 19:59 pset, NULL, and COPY-reporting John Bell <jzb@ornl.gov>
  2015-06-03 18:41 ` Re: pset, NULL, and COPY-reporting David G. Johnston <david.g.johnston@gmail.com>
@ 2015-06-03 21:12   ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 3+ messages in thread

From: Tom Lane @ 2015-06-03 21:12 UTC (permalink / raw)
  To: David G. Johnston <david.g.johnston@gmail.com>; +Cc: John Bell <jzb@ornl.gov>; pgsql-admin

"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Tuesday, June 2, 2015, John Bell <jzb@ornl.gov> wrote:
>> Due to some level of ignorance at install-time, our "psql" clients on two
>> different production computers appear to have different values for /null/:

> You can decide what to have null output as using pset variables.  See the
> documentation.  The default could have changed between versions, maybe...

No, I don't think so --- but possibly one machine has a setting in
~/.psqlrc that the other doesn't.

>> 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.

> Pretty sure the copy behavior is always on but version dependent.

Yeah, psql 9.4 started doing that.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2015-06-03 21:12 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2015-06-02 19:59 pset, NULL, and COPY-reporting John Bell <jzb@ornl.gov>
2015-06-03 18:41 ` David G. Johnston <david.g.johnston@gmail.com>
2015-06-03 21:12   ` Tom Lane <tgl@sss.pgh.pa.us>

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