Re: pset, NULL, and COPY-reporting

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: pset, NULL, and COPY-reporting
Дата
Msg-id CAKFQuwZg5n43a_aQ7difbNHJ_+apGXxydcNP8TuV076WGjqDcg@mail.gmail.com
обсуждение исходный текст
Ответ на pset, NULL, and COPY-reporting  ("John Bell" <jzb@ornl.gov>)
Ответы Re: pset, NULL, and COPY-reporting  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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.

В списке pgsql-admin по дате отправления:

Предыдущее
От: "John Bell"
Дата:
Сообщение: pset, NULL, and COPY-reporting
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pset, NULL, and COPY-reporting