Re: psql --batch

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql --batch
Date: 2017-08-28 07:22:42
Message-ID: CAFj8pRB3BVkL_6+WgPWsk2XsPidyFze8rMzP7M6i9T0-iDkWkA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2017-08-28 8:56 GMT+02:00 Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>:

>
> I find myself regurgitating the incantation
>>
>> psql -qAtX -v ON_ERRORS_STOP=1
>>
>> quite a bit. It's not ... super friendly.
>>
>> It strikes me that we could possibly benefit from a 'psql --batch' option.
>>
>> Thoughts?
>>
>
> The link between -qAtX and "batch" is not that fully obvious, especially
> the unaligned tuples-only part. If so, why not some -F <tab> as well?
>
> ISTM that the real pain is the "-v ON_ERRORS_STOP=1" which I occasionally
> encountered as well, the other one letter ones are not too bad. Maybe it
> would be enough to have a shortcut for this one, say "-B"?
>

I agree with last sentence. I don't think so -qAtX are expected always, but
"-v ON_ERROS_STOP=1" is pretty often.

What do you think about long option "---on-errors-stop" ?

Regards

Pavel

> alias?
>
> --
> Fabien.
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2017-08-28 07:33:09 Re: psql --batch
Previous Message Michael Paquier 2017-08-28 07:19:47 Re: Make pg_regress print a connstring with sockdir