Re: trivial improvement to system_or_bail - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: trivial improvement to system_or_bail
Date
Msg-id F3C95652-4FE1-4C33-9E19-9ADA1BF3AF15@yesql.se
Whole thread Raw
In response to Re: trivial improvement to system_or_bail  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
> On 6 Jul 2021, at 23:59, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:

> Failures now look like this, respectively:
>
> Bailout called.  Further testing stopped:  failed to execute command "finitdb -D
/home/alvherre/Code/pgsql-build/master/src/test/recovery/tmp_check/t_019_replslot_limit_primary_data/pgdata-A trust -N
--wal-segsize=1":No such file or directory 
>
> Bailout called.  Further testing stopped:  command "initdb -0D
/home/alvherre/Code/pgsql-build/master/src/test/recovery/tmp_check/t_019_replslot_limit_primary_data/pgdata-A trust -N
--wal-segsize=1"exited with value 1 
>
> Bailout called.  Further testing stopped:  command "initdb -0D
/home/alvherre/Code/pgsql-build/master/src/test/recovery/tmp_check/t_019_replslot_limit_primary_data/pgdata-A trust -N
--wal-segsize=1"died with signal 11 
>
>
> Previously it was just
>
> Bailout called.  Further testing stopped:  system initdb failed

That is no doubt going to be helpful, thanks!

--
Daniel Gustafsson        https://vmware.com/




pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: ExecRTCheckPerms() and many prunable partitions
Next
From: Peter Eisentraut
Date:
Subject: Re: PostgreSQL-13.3 parser.y with positional references by named references