From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
cc: John Bell <jzb@ornl.gov>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: pset, NULL, and COPY-reporting
In-reply-to: 
 <CAKFQuwZg5n43a_aQ7difbNHJ_+apGXxydcNP8TuV076WGjqDcg@mail.gmail.com>
References: <006c01d09d6e$af1de600$0d59b200$@ornl.gov>
 <CAKFQuwZg5n43a_aQ7difbNHJ_+apGXxydcNP8TuV076WGjqDcg@mail.gmail.com>
Comments: In-reply-to "David G. Johnston" <david.g.johnston@gmail.com>
 message dated "Wed, 03 Jun 2015 14:41:54 -0400"
Date: Wed, 03 Jun 2015 17:12:13 -0400
Message-ID: <28183.1433365933@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

"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