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

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use abort() instead of exit() to abort library functions
Date: 2012-01-30 19:49:47
Message-ID: E1RrxEZ-0001Ak-BM@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2012-01-30 20:50:28 Re: [COMMITTERS] pgsql: Make group commit more effective.
Previous Message Robert Haas 2012-01-30 18:27:50 Re: [COMMITTERS] pgsql: Make group commit more effective.