Re: Cleaning up historical portability baggage

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, 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-12 07:07:18
Message-ID: 5ccec641-9c06-6083-c22e-931fa99f3e81@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11.08.22 19:19, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
>> On 2022-08-11 10:52:51 -0400, Tom Lane wrote:
>>> -- I won't be too surprised if we get pushback on that after 15.0 is out.
>
>> From what angle?
>
> If I knew that, it'd be because we'd already received the pushback.
> I'm just suspicious that very little beta testing happens on Windows,
> and what does is probably mostly people running up-to-date Windows.
> So I think there's plenty of chance for "hey, this no longer works"
> complaints later. Maybe we'll be able to reject it all with "sorry,
> we desupported that version of Windows", but I dunno.

What is changing in PG15 about this? Unix-domain sockets on Windows are
supported as of PG13.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2022-08-12 07:12:15 Re: Cleaning up historical portability baggage
Previous Message John Naylor 2022-08-12 06:59:30 Re: fix typos