From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql --batch |
Date: | 2017-08-28 07:56:41 |
Message-ID: | CAMsr+YHiaXiKUEBRuGysR8ZNN3dVoysMo=Je+OTLUcD2HpWB1g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 28 August 2017 at 15:34, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
>
> 2017-08-28 9:33 GMT+02:00 Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>:
>
>>
>> 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_ERRORS_STOP=1" is pretty often.
>>>
>>
>> Yep. I often "\set" that in the script.
>>
>> What do you think about long option "--on-errors-stop" ?
>>>
>>
>> It does not really relieve the typing pain Craig is complaining about,
>> but it would be ok as the long option version if -B is added, and it is
>> auto-completion friendly.
>
>
>
This doesn't really address the original issue though, that it's far from
obvious how to easily and correctly script psql.
I guess there's always the option of a docs patch for that. *shrug*
I'll see what others have to say.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2017-08-28 07:59:01 | Re: pgbench: Skipping the creating primary keys after initialization |
Previous Message | Craig Ringer | 2017-08-28 07:52:13 | Re: Make pg_regress print a connstring with sockdir |