Re: Cleaning up historical portability baggage

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Cleaning up historical portability baggage
Date: 2022-08-05 09:26:04
Message-ID: CA+hUKGKgstEDsVbqKPFajRCAaCemxr8b89Gku0CG6s=zcK01sw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I've now pushed all of these except the --disable-thread-safety one,
which I'm still contemplating. So far all green on the farm (except
known unrelated breakage). But that's just the same-day animals...

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2022-08-05 09:58:23 Re: enable/disable broken for statement triggers on partitioned tables
Previous Message Thomas Munro 2022-08-05 09:17:45 Re: Checking pgwin32_is_junction() errors