Re: Add SHELL_EXIT_CODE to psql
| От | Tom Lane |
|---|---|
| Тема | Re: Add SHELL_EXIT_CODE to psql |
| Дата | |
| Msg-id | 950438.1679331690@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Add SHELL_EXIT_CODE to psql (Corey Huinker <corey.huinker@gmail.com>) |
| Ответы |
Re: Add SHELL_EXIT_CODE to psql
|
| Список | pgsql-hackers |
Corey Huinker <corey.huinker@gmail.com> writes:
> 128+N is implemented.
I think this mostly looks OK, but:
* I still say there is no basis whatever for believing that the result
of ferror() is an exit code, errno code, or anything else with
significance beyond zero-or-not. Feeding it to wait_result_to_exit_code
as you've done here is not going to do anything but mislead people in
a platform-dependent way. Probably should set exit_code to -1 if
ferror reports trouble.
* Why do you have wait_result_to_exit_code defaulting to return 0
if it doesn't recognize the code as either WIFEXITED or WIFSIGNALED?
That seems pretty misleading; again -1 would be a better idea.
regards, tom lane
В списке pgsql-hackers по дате отправления: