Re: pset, NULL, and COPY-reporting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"David G. Johnston" <david.g.johnston@xxxxxxxxx> writes:
> On Tuesday, June 2, 2015, John Bell <jzb@xxxxxxxx> 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@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux