Re: Badly designed error reporting code in controldata_utils.c
| От | Joe Conway |
|---|---|
| Тема | Re: Badly designed error reporting code in controldata_utils.c |
| Дата | |
| Msg-id | 56DE0C4A.2080300@joeconway.com обсуждение |
| Ответ на | Re: Badly designed error reporting code in controldata_utils.c (Joe Conway <mail@joeconway.com>) |
| Ответы |
Re: Badly designed error reporting code in controldata_utils.c
|
| Список | pgsql-hackers |
On 03/07/2016 08:02 AM, Joe Conway wrote: > On 03/06/2016 07:34 PM, Tom Lane wrote: >> Joe Conway <mail@joeconway.com> writes: >>> On 03/06/2016 05:47 PM, Tom Lane wrote: >>>> That's much better, but is there a reason you're using exit(2) >>>> and not exit(EXIT_FAILURE) ? >> >>> Only because I was trying to stick with what was originally in >>> src/bin/pg_controldata/pg_controldata.c >> >> Meh. It looks to me like the standard way to handle this >> for code in src/common/ is exit(EXIT_FAILURE). > > I have no issue with using EXIT_FAILURE, but note: Committed/pushed with exit(EXIT_FAILURE) Joe -- Crunchy Data - http://crunchydata.com PostgreSQL Support for Secure Enterprises Consulting, Training, & Open Source Development
В списке pgsql-hackers по дате отправления: