| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Jacob Champion <pchampion(at)vmware(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>, info(at)cspug(dot)cz |
| Subject: | Re: Preventing abort() and exit() calls in libpq |
| Date: | 2021-07-03 22:44:20 |
| Message-ID: | 1288324.1625352260@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Noah Misch <noah(at)leadboat(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-07-03 22:59:49 | Re: Reducing the cycle time for CLOBBER_CACHE_ALWAYS buildfarm members |
| Previous Message | Noah Misch | 2021-07-03 21:46:58 | Re: Preventing abort() and exit() calls in libpq |