| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: port conflicts when running tests concurrently on windows. |
| Date: | 2021-12-09 13:35:37 |
| Message-ID: | 7a217775-e9a5-f49a-c7f1-ba277b07e9e9@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-12-09 13:35:41 | Re: The "char" type versus non-ASCII characters |
| Previous Message | Tom Lane | 2021-12-09 13:31:23 | Re: Replace uses of deprecated Python module distutils.sysconfig |