Hi,
On Mon, Dec 27, 2021 at 12:31:07PM -0500, Tom Lane wrote:
> Justin Pryzby writes:
> > I think the current behavior of the regression test SQL scripts is exactly
> > the
> > opposite of what's desirable for almost all other scripts. The attached
> > makes
> > ON_ERROR_STOP the default, and
Justin Pryzby writes:
> I think the current behavior of the regression test SQL scripts is exactly the
> opposite of what's desirable for almost all other scripts. The attached makes
> ON_ERROR_STOP the default, and runs the regression tests with ON_ERROR_STOP=0.
> Is it viable to consider
po 27. 12. 2021 v 17:10 odesílatel Justin Pryzby
napsal:
> On Mon, Dec 06, 2021 at 09:08:56AM -0600, Justin Pryzby wrote:
> > I raised this issue a few years ago.
> >
> https://www.postgresql.org/message-id/20181217175841.GS13019%40telsasoft.com
> >
> > |[pryzbyj@database ~]$ psql -v
On Mon, Dec 06, 2021 at 09:08:56AM -0600, Justin Pryzby wrote:
> I raised this issue a few years ago.
> https://www.postgresql.org/message-id/20181217175841.GS13019%40telsasoft.com
>
> |[pryzbyj@database ~]$ psql -v VERBOSITY=terse ts -xtc 'ONE' -c "SELECT
> 'TWO'"; echo "exit status $?"
>
I raised this issue a few years ago.
https://www.postgresql.org/message-id/20181217175841.GS13019%40telsasoft.com
|[pryzbyj@database ~]$ psql -v VERBOSITY=terse ts -xtc 'ONE' -c "SELECT 'TWO'";
echo "exit status $?"
|ERROR: syntax error at or near "ONE" at character 1
|?column? | TWO
|
|exit
At Tue, 18 Dec 2018 10:24:39 -0600, Justin Pryzby wrote:
> I think ON_ERROR_STOP would control whether the script stops, but it should
> fail the exit status should reflect any error in the last command. The
> shell does that even without set -e.
Let me correct my own language:
| I think
On Wed, Jan 30, 2019 at 6:38 PM Kyotaro HORIGUCHI
wrote:
> I guess the reason is that psql is widely used with just a single
> -c command and acutually the fix breaks the cases. So it doesn't
> seem back-pachable but it is apparently contradicting to
> documentation, which seems perfectly
At Thu, 31 Jan 2019 10:37:28 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
wrote in
<20190131.103728.153290385.horiguchi.kyot...@lab.ntt.co.jp>
> > I think ON_ERROR_STOP would control whether the script stops, but it should
> > fail the exit status should reflect any error in the last command.
Hello.
At Tue, 18 Dec 2018 10:24:39 -0600, Justin Pryzby wrote
in <20181218162439.gb8...@telsasoft.com>
> On Tue, Dec 18, 2018 at 05:13:40PM +0900, Kyotaro HORIGUCHI wrote:
> > $ psql postgres -v ON_ERROR_STOP=0 -f ~/work/y.txt ; echo $?
> > $ psql postgres -v ON_ERROR_STOP=0 < ~/work/y.txt ;
On Tue, Dec 18, 2018 at 05:13:40PM +0900, Kyotaro HORIGUCHI wrote:
> $ psql postgres -v ON_ERROR_STOP=0 -f ~/work/y.txt ; echo $?
> $ psql postgres -v ON_ERROR_STOP=0 < ~/work/y.txt ; echo $?
> c) psql postgres -v ON_ERROR_STOP=0 -c foo -c 'select 1'; echo $?
> d) psql postgres -v
út 18. 12. 2018 v 9:14 odesílatel Kyotaro HORIGUCHI <
horiguchi.kyot...@lab.ntt.co.jp> napsal:
> Hello.
>
> At Mon, 17 Dec 2018 11:58:41 -0600, Justin Pryzby
> wrote in <20181217175841.gs13...@telsasoft.com>
> > Our deployment script failed to notice dozens of commands failed in a
> >
Hello.
At Mon, 17 Dec 2018 11:58:41 -0600, Justin Pryzby wrote
in <20181217175841.gs13...@telsasoft.com>
> Our deployment script failed to notice dozens of commands failed in a
> transaction block and I only noticed due to keeping full logs and monitoring
> for error_severity>'LOG'. I would
Our deployment script failed to notice dozens of commands failed in a
transaction block and I only noticed due to keeping full logs and monitoring
for error_severity>'LOG'. I would have thought that exit status would be
nonzero had an error occured in an earlier script.
The docs since PG9.6 say:
13 matches
Mail list logo
