pgsql: Further restrict the scope of no-exit()-in-libpq test.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Further restrict the scope of no-exit()-in-libpq test.
Date: 2021-07-03 15:21:44
Message-ID: E1lzhSi-00045q-8D@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Further restrict the scope of no-exit()-in-libpq test.

Disable this check altogether in --enable-coverage builds,
because newer versions of gcc insert exit() as well as abort()
calls for that. Also disable it on AIX and Solaris, because
those platforms tend to provide facilities such as libldap
as static libraries, which then get included in libpq's shlib.
We can't expect such libraries to honor our coding rules.
(That platform list might need additional tweaking, but I think
this is enough to keep the buildfarm happy.)

Per reports from Jacob Champion and Noah Misch.

Discussion: https://postgr.es/m/3128896.1624742969@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/792259591c0fc19c42247fc7668b1064d1e850d4

Modified Files
--------------
src/interfaces/libpq/Makefile | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2021-07-04 06:48:08 pgsql: Cleanup some aggregate code in the executor
Previous Message Bruce Momjian 2021-07-03 00:43:20 pgsql: doc: adjust "cities" example to be consistent with other SQL