Re: Make ON_ERROR_STOP stop on shell script failure
От | torikoshia |
---|---|
Тема | Re: Make ON_ERROR_STOP stop on shell script failure |
Дата | |
Msg-id | 6fd74d4bf62664b0320cde3f7a48f522@oss.nttdata.com обсуждение исходный текст |
Ответ на | Re: Make ON_ERROR_STOP stop on shell script failure (bt22nakamorit <bt22nakamorit@oss.nttdata.com>) |
Ответы |
Re: Make ON_ERROR_STOP stop on shell script failure
|
Список | pgsql-hackers |
On 2022-09-20 15:15, bt22nakamorit wrote: > I edited the documentation for ON_ERROR_STOP. > Any other suggestions? Thanks for the patch! > 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? -- Regards, -- Atsushi Torikoshi NTT DATA CORPORATION
В списке pgsql-hackers по дате отправления: