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

From John Naylor
Subject Re: Cleaning up historical portability baggage
Date
Msg-id CAFBsxsHnK5YAzvSVXo0=8kqrKt-OSHgDFDFVR0HTq-qADbJqJA@mail.gmail.com
Whole thread Raw
In response to Re: Cleaning up historical portability baggage  (Ibrar Ahmed <ibrar.ahmad@gmail.com>)
Responses Re: Cleaning up historical portability baggage
List pgsql-hackers
On Thu, Sep 15, 2022 at 3:11 PM Ibrar Ahmed <ibrar.ahmad@gmail.com> wrote:
> The patch does not apply successfully; please rebase the patch.

There's a good reason for that -- the latest one was committed two
weeks ago. The status should still be waiting on author, though,
namely for:

On Fri, Aug 26, 2022 at 5:28 AM Thomas Munro <thomas.munro@gmail.com> wrote:
> Remaining things from this thread:
>  * removing --disable-thread-safety
>  * removing those vestigial HAVE_XXX macros (one by one analysis and patches)
>  * making Unix sockets secure for Windows in tests

-- 
John Naylor
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: Counterintuitive behavior when toast_tuple_target < TOAST_TUPLE_THRESHOLD
Next
From: Justin Pryzby
Date:
Subject: Re: failing to build preproc.c on solaris with sun studio