Re: Cleaning up historical portability baggage - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Cleaning up historical portability baggage
Date
Msg-id CA+hUKGJSqeMby0WwE_E6_3X91OzSZu4a=YSEzoVB42tdE4HBjg@mail.gmail.com
Whole thread Raw
In response to Re: Cleaning up historical portability baggage  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Jul 24, 2022 at 11:11 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thomas Munro <thomas.munro@gmail.com> writes:
> > Some of these depend on SUSv2 options (not just "base"), but we
> > already do that (fsync, ...) and they're all features that are by now
> > ubiquitous, which means the fallback code is untested and the probes
> > are pointless.
>
> Reading this, it occurred to me that it'd be interesting to scrape
> all of the latest configure results from the buildfarm, and see which
> tests actually produce more than one answer among the set of tested
> platforms.  Those that don't could be targets for further simplification,
> or else an indicator that we'd better go find some more animals.
>
> Before I go off and do that, though, I wonder if you already did.

Yeah, here are the macros I scraped yesterday, considering the latest
results from machines that did something in the past week.

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Cleaning up historical portability baggage
Next
From: Zhihong Yu
Date:
Subject: redacting password in SQL statement in server log