Horton

Re: Preventing abort() and exit() calls in libpq

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "alvherre@alvh.no-ip.org" <alvherre@alvh.no-ip.org>
Cc: Jacob Champion <pchampion@vmware.com>, "daniel@yesql.se" <daniel@yesql.se>, "info@cspug.cz" <info@cspug.cz>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "michael@paquier.xyz" <michael@paquier.xyz>
Date: 2021-07-02T23:08:41Z
Lists: pgsql-hackers 
"alvherre@alvh.no-ip.org" <alvherre@alvh.no-ip.org> writes:
> gcc here is 8.3.0.

Hmmm ... mine is 8.4.1.

I'm about to go out to dinner, but will check into this with some
newer gcc versions later.

			regards, tom lane

Commits

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

  2. Improve build-time check that libpq doesn't call exit().

  3. Fix portability fallout from commit dc227eb82.

  4. Add a build-time check that libpq doesn't call exit() or abort().