13.01.2022 09:36, Thomas Munro wrote: > On Wed, Jan 12, 2022 at 8:00 PM Alexander Lakhin <exclus...@gmail.com> wrote: >> By the look of things, you are right and this is the localhost-only issue. > But can't that be explained with timing races? You change some stuff > around and it becomes less likely that you get a FIN to arrive in a > super narrow window, which I'm guessing looks something like: recv -> > EWOULDBLOCK, [receive FIN], wait -> FD_CLOSE, wait [hangs]. Note that > it's not happening on several Windows BF animals, and the ones it is > happening on only do it only every few weeks. But I still see the issue when I run both test parts on a single machine: first instance is `vcregress taptest src\test\restart` and the second `set NO_TEMP_INSTALL=1 & vcregress taptest contrib/postgres_fdw` (see attachment).
I'll try new tests and continue investigation later today/tomorrow. Thanks! Best regards, Alexander
