Re: [HACKERS] psql --batch

Поиск
Список
Период
Сортировка
От Craig Ringer
Тема Re: [HACKERS] psql --batch
Дата
Msg-id CAMsr+YEnie9jU9nOs0oXJedE0t-CF3RM1UNugAc4xcVe82TRWw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] psql --batch  (Fabien COELHO <coelho@cri.ensmp.fr>)
Ответы Re: [HACKERS] psql --batch  (Pavel Stehule <pavel.stehule@gmail.com>)
Список pgsql-hackers
On 28 August 2017 at 16:23, Fabien COELHO <coelho@cri.ensmp.fr> wrote:

This doesn't really address the original issue though, that it's far from
obvious how to easily and correctly script psql.

That is another interesting argument. I understood that the issue was having to type these options, but now it is also to remember which one are relevant and wanted, which is a little different and more justifiable as an option.

On that account, ISTM that '|' as a field separator is debatable, that pager should be turned off... and maybe a few other things.


Good point re pager, though it's turned off automatically when stdout isn't a terminal, so in practice that'll only matter if you're using something like 'expect' that uses a pty. Still worth doing.

I agree that | is a bit iffy, but so's anything really. null bytes aren't usable for all scripts, and nothing else cannot also be output in the data its self. No easy answers there. In cases where I expect that to be an issue I sometimes use \COPY ... TO STDOUT WITH (FORMAT CSV) though.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

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

Предыдущее
От: Ryan Murphy
Дата:
Сообщение: [HACKERS] 1 test fails in make installcheck-world - database"regress_ecpg_user2" does not exist
Следующее
От: Antonin Houska
Дата:
Сообщение: Re: [HACKERS] WIP: Separate log file for extension