On mån, 2011-12-05 at 15:04 -0300, Alvaro Herrera wrote:
Having had to battle some exit() calls in the PHP interpreter back
when
I was working in PL/php, I agree that they shouldn't be there --
abort()
seems more appropriate if the system is truly busted. As for the
fr-print.c code, I'm not
Debian's package policy and quality check tool lintian reports the
following (among other things) on the postgresql-9.1 (and earlier)
packages:
X: libpq5: shlib-calls-exit usr/lib/libpq.so.5.4
X: libecpg6: shlib-calls-exit usr/lib/libecpg.so.6.3
which is explained as
I: shlib-calls-exit
N:
N:
Excerpts from Peter Eisentraut's message of lun dic 05 14:27:41 -0300 2011:
The cases in libpq are
* various places in fe-print.c calling exit(1) when malloc fails,
presumably having run out of memory, and
* in libpq-int.h the macro PGTHREAD_ERROR, which is called in
