Re: Make ON_ERROR_STOP stop on shell script failure

From: bt22nakamorit <bt22nakamorit(at)oss(dot)nttdata(dot)com>
To: torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Make ON_ERROR_STOP stop on shell script failure
Date: 2022-09-29 02:29:40
Message-ID: 36360350378935c823a9dbbff5b2e54e@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2022-09-28 21:49 に torikoshia さんは書きました:
>> if (result == 127 || result == -1)
>> {
>> pg_log_error("\\!: failed");
>> return false;
>> }
>> else if (result != 0) {
>> pg_log_error("command failed");
>> return false;
>
> Since it would be hard to understand the cause of failures from these
> two messages, it might be better to clarify them in the messages.
>
> The former comes from failures of child process creation or execution
> on it and the latter occurs when child process creation and execution
> succeeded but the return code is not 0, doesn't it?
>
>
> I also felt it'd be natural that the latter message also begins with
> "\\!" since both message concerns with \!.
>
> How do you think?

Thank you for the feedback!
I agree that the messages should be more clear.
\\!: command was not executed
\\!: command failed
Would these two messages be enough to describe the two cases?

Tatsu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2022-09-29 02:40:38 Re: identifying the backend that owns a temporary schema
Previous Message Tom Lane 2022-09-29 02:14:11 Re: longfin and tamandua aren't too happy but I'm not sure why