Re: Why doesn't src/backend/port/win32/socket.c implement bind()? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Why doesn't src/backend/port/win32/socket.c implement bind()?
Date
Msg-id 19658.1460554394@sss.pgh.pa.us
Whole thread Raw
In response to Re: Why doesn't src/backend/port/win32/socket.c implement bind()?  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Why doesn't src/backend/port/win32/socket.c implement bind()?  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Michael Paquier <michael.paquier@gmail.com> writes:
> On Wed, Apr 13, 2016 at 9:06 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> If there's other stuff using high ports on a particular buildfarm machine,
>> you'd expect occasional random test failures due to this.  The observed
>> fact that some buildfarm critters are much more prone to this type of
>> failure than others is well explained by this hypothesis.

> Each test run uses its own custom unix_socket_directories, PGHOST is
> enforced to use it, and all the port tests go through that as well.

By that argument, we don't need the free-port-searching code on Unix at
all.  But this discussion is mostly about Windows machines.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Optimization for updating foreign tables in Postgres FDW
Next
From: Abhijit Menon-Sen
Date:
Subject: Re: Pglogical questions and problems