pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: John Naylor <john.naylor@enterprisedb.com>
Cc: Ibrar Ahmed <ibrar.ahmad@gmail.com>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Andres Freund <andres@anarazel.de>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Robert Haas <robertmhaas@gmail.com>
Subject: Re: Cleaning up historical portability baggage
Date: Thu, 15 Sep 2022 09:55:20 -0400
Message-ID: <3265442.1663250120@sss.pgh.pa.us> (raw)
In-Reply-To: <CAFBsxsHnK5YAzvSVXo0=8kqrKt-OSHgDFDFVR0HTq-qADbJqJA@mail.gmail.com>
References: <295419.1659918447@sss.pgh.pa.us>
	<CA+hUKGK=N8W2uFPdJr07Rs4dgRtbzKaYvCaPQasX3S8=aTO5PQ@mail.gmail.com>
	<747620.1660002360@sss.pgh.pa.us>
	<CA+hUKG+L_3brvh=8e0BW_VfX9h7MtwgN=nFHP5o7X2oZucY9dg@mail.gmail.com>
	<CA+hUKGJdfTFtZXQ8P8CZtyx1k=mHcOD9savHVR2cjSSVp5Uirw@mail.gmail.com>
	<CA+hUKGLW6dWAJYQ4q1wXED78L_=tZp0LKi-BNjEaEnqfyWB4vw@mail.gmail.com>
	<360948.1660414060@sss.pgh.pa.us>
	<CA+hUKG+46-J6ALM65ka7ObG2=_zeMy1EyZDcY8QnENayfMzMqQ@mail.gmail.com>
	<CA+hUKGKErNfhmvb_H0UprEmp4LPzGN06yR2_0tYikjzB-2ECMw@mail.gmail.com>
	<CA+hUKGJZErt=_muvi3Q3_tc=nP2=SyZtBpx_-gWYwNZOcn2_EA@mail.gmail.com>
	<20220825194729.5cgvx26ekbtmvjzg@awork3.anarazel.de>
	<CA+hUKG+a2mfK1ydpoLi2tnLZFZKq_kdB17F7fafFpb8aHETxZw@mail.gmail.com>
	<2923412.1661722825@sss.pgh.pa.us>
	<CA+hUKGJAgyWE4x94fz1BLqM0xogEujA7==Q-PQsfW9QByqYG4Q@mail.gmail.com>
	<CALtqXTcb7baV39KODc+2xN4y_8794yDkrbcwi2y1SkGxUs7OEA@mail.gmail.com>
	<CAFBsxsHnK5YAzvSVXo0=8kqrKt-OSHgDFDFVR0HTq-qADbJqJA@mail.gmail.com>

John Naylor <john.naylor@enterprisedb.com> writes:
> 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

I imagine we should just close the current CF entry as committed.
There's no patch in existence for any of those TODO items, and
I didn't think one was imminent.

			regards, tom lane





view thread (108+ messages)  latest in thread

Message-ID: <3265442.1663250120@sss.pgh.pa.us>
Permalink:  ../3265442.1663250120@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3265442.1663250120@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, john.naylor@enterprisedb.com, ibrar.ahmad@gmail.com, thomas.munro@gmail.com, andres@anarazel.de, peter.eisentraut@enterprisedb.com, andrew@dunslane.net, robertmhaas@gmail.com
  Subject: Re: Cleaning up historical portability baggage
  In-Reply-To: <3265442.1663250120@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox