Re: port conflicts when running tests concurrently on windows.

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: port conflicts when running tests concurrently on windows.
Date: 2021-12-15 14:10:40
Message-ID: 19f57340-0ccb-92ef-f234-f5f46932779c@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 13.12.21 20:33, Andres Freund wrote:
>> pg_regress.c at remove_temp() is still there. These things should probably
>> be addressed before we can consider making this the default.
>
> Hm, not immediately obvious what to do about this. Do you know if windows has
> restrictions around the length of unix domain sockets? If not, I wonder if it
> could be worth using the data directory as the socket path on windows instead
> of the separate temp directory?

According to src/include/port/win32.h, it's the same 108 or so bytes
that everyone else uses. That might not be the kernel limit, however,
just the way the external API is defined.

After the reading the material again, I think that comment might be
overly cautious. The list of things not to do in a signal handler on
Windows is not significantly different than those for say Linux, yet we
do a lot of them anyway. I'm tempted to just ignore the advice and do
it anyway, while ignoring errors, which is what it already does.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2021-12-15 14:42:45 Re: Adding CI to our tree
Previous Message Tomas Vondra 2021-12-15 13:58:39 Re: logical decoding and replication of sequences