Re: port conflicts when running tests concurrently on windows.

On 12/9/21 08:35, Peter Eisentraut wrote:
> On 09.12.21 03:44, Thomas Munro wrote:
>> On Thu, Dec 9, 2021 at 11:46 AM Andres Freund<andres(at)anarazel(dot)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?

Probably not if they have been updated. I have Windows machines
substantially older that 2018 but now running versions dated later.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com