Re: Preventing abort() and exit() calls in libpq - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Preventing abort() and exit() calls in libpq
Date
Msg-id 1288324.1625352260@sss.pgh.pa.us
Whole thread Raw
In response to Re: Preventing abort() and exit() calls in libpq  (Noah Misch <noah@leadboat.com>)
Responses Re: Preventing abort() and exit() calls in libpq  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
Noah Misch <noah@leadboat.com> writes:
> On Sat, Jul 03, 2021 at 10:45:59AM -0400, Tom Lane wrote:
>> What I'm now thinking about is restricting the test to only be run on
>> platforms where use of foo.a libraries is deprecated, so that we can
>> be pretty sure that we won't hit this situation.  Even if we only
>> run the test on Linux, that'd be plenty to catch any mistakes.

> Hmm.  Static libraries are the rarer case on both AIX and Linux, but I'm not
> aware of a relevant deprecation on either platform.  If it comes this to, I'd
> be more inclined to control the Makefile rule with an environment variable
> (e.g. ENFORCE_LIBC_CALL_RESTRICTIONS) instead of reacting to the platform.

That'd require buildfarm owner intervention, as well as intervention
by users.  Which seems like exporting our problems onto them.  I'd
really rather not go that way if we can avoid it.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Preventing abort() and exit() calls in libpq
Next
From: Tom Lane
Date:
Subject: Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members