Re: [HACKERS] psql --batch - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] psql --batch
Date
Msg-id CAFj8pRDmKVZFvc7T6MsrQJkqqZqWhVZGvVX8tPmOUeNwzmYWOA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] psql --batch  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: [HACKERS] psql --batch
List pgsql-hackers


2017-08-28 11:05 GMT+02:00 Craig Ringer <craig@2ndquadrant.com>:
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.

I don't doubt about a sense of this configuration - but this specific combination depends on usage - so I don't think so using special option is good idea.

Regards

Pavel
 

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

pgsql-hackers by date:

Previous
From: Kyotaro HORIGUCHI
Date:
Subject: Re: [HACKERS] Race between SELECT and ALTER TABLE NO INHERIT
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: [HACKERS] Restricting maximum keep segments by repslots