Horton

Re: port conflicts when running tests concurrently on windows.

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Thomas Munro <thomas.munro@gmail.com>, Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-12-09T13:35:37Z
Lists: pgsql-hackers 
On 09.12.21 03:44, Thomas Munro wrote:
> On Thu, Dec 9, 2021 at 11:46 AM Andres Freund<andres@anarazel.de>  wrote:
>> Is it perhaps time to to use unix sockets on windows by default
>> (i.e. PG_TEST_USE_UNIX_SOCKETS), at least when on a new enough windows?

Makes sense to get this to work, at least as an option.

> Makes sense.  As a data point, it looks like this feature is in all
> supported releases of Windows.  It arrived in 1803, already EOL'd, and
> IIUC even a Windows Server 2016 "LTSC" system that's been disconnected
> from the internet and refusing all updates reaches "mainstream EOL"
> next month.

I believe the "18" in "1803" refers to 2018.  We have Windows buildfarm 
members that mention 2016 and 2017 in their title.  Would those be in 
trouble?

Commits

  1. Make PG_TEST_USE_UNIX_SOCKETS work for tap tests on windows.

  2. Allow using Unix-domain sockets on Windows in tests

  3. Enable Unix-domain sockets support on Windows