pgsql: Use abort() instead of exit() to abort library functions

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема pgsql: Use abort() instead of exit() to abort library functions
Дата
Msg-id E1RrxEZ-0001Ak-BM@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Use abort() instead of exit() to abort library functions

In some hopeless situations, certain library functions in libpq and
libpgport quit the program.  Use abort() for that instead of exit(),
so we don't interfere with the normal exit codes the program might
use, we clearly signal the abnormal termination, and the caller has a
chance of catching the termination.

This was originally pointed out by Debian's Lintian program.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/c6ea8ccea6bf23501962ddc7ac9ffdb99c8643e1

Modified Files
--------------
src/interfaces/libpq/fe-print.c  |   16 ++++++++--------
src/interfaces/libpq/libpq-int.h |    2 +-
src/port/path.c                  |    2 +-
3 files changed, 10 insertions(+), 10 deletions(-)


В списке pgsql-committers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: pgsql: PL/Python: Add result metadata functions
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: pgsql: Fix bug in the new wait-until-lwlock-is-free mechanism.