Re: proposal: new long psql parameter --on-error-stop

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Erik Rijkers <er(at)xs4all(dot)nl>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: new long psql parameter --on-error-stop
Date: 2014-02-28 21:58:43
Message-ID: CAFj8pRDcOUQ=kONMwBn+BWx7k3apE=VOa9xEiJHE0ECdzxQSew@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2014-02-28 22:52 GMT+01:00 Erik Rijkers <er(at)xs4all(dot)nl>:

> On Fri, February 28, 2014 22:38, Tom Lane wrote:
> > Andrew Dunstan <andrew(at)dunslane(dot)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
>

can be

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-02-28 22:01:45 Re: proposal: new long psql parameter --on-error-stop
Previous Message Erik Rijkers 2014-02-28 21:52:23 Re: proposal: new long psql parameter --on-error-stop