Re: proposal: new long psql parameter --on-error-stop - Mailing list pgsql-hackers

From Erik Rijkers
Subject Re: proposal: new long psql parameter --on-error-stop
Date
Msg-id a7ae67c1464742a752fc44233e345ad1.squirrel@webmail.xs4all.nl
Whole thread Raw
In response to Re: proposal: new long psql parameter --on-error-stop  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: proposal: new long psql parameter --on-error-stop  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: proposal: new long psql parameter --on-error-stop  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Fri, February 28, 2014 22:38, Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>>> Well, then we just have to add more info to --help
>
>> +1 for at least doing that. I found it annoying just the other day not
>> to find it in plsql's --help output, in a moment of brain fade when I
>> forgot how to spell it. So it's not just beginners who can benefit, it's
>> people like me whose memory occasionally goes awry.
>
> No objection in principle, but what are we talking about exactly?
> Adding some new backslash command that lists all the variables that have
> special meanings?  I'm not sure that the main --help output is the place
> for this, because that only covers psql's command line switches (and
> is plenty long enough already).
>
>             regards, tom lane

Perhaps this compromise:
 -v, --set=, --variable=NAME=VALUE                          set psql variable NAME to VALUE e.g.: -v ON_ERROR_STOP=1

this would not lengthen and not broaden the output of psql --help






pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: new long psql parameter --on-error-stop
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: new long psql parameter --on-error-stop