Re: trivial improvement to system_or_bail

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: trivial improvement to system_or_bail
Date: 2021-07-07 07:13:58
Message-ID: F3C95652-4FE1-4C33-9E19-9ADA1BF3AF15@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 6 Jul 2021, at 23:59, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2021-07-07 08:28:38 Re: PostgreSQL-13.3 parser.y with positional references by named references
Previous Message Amit Langote 2021-07-07 07:12:49 Re: ExecRTCheckPerms() and many prunable partitions