Why doesn't src/backend/port/win32/socket.c implement bind()?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Why doesn't src/backend/port/win32/socket.c implement bind()?
Date: 2016-01-10 18:25:40
Message-ID: 4065.1452450340@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Some of the Windows buildfarm members occasionally fail like this:

LOG: could not bind IPv4 socket: No error
HINT: Is another postmaster already running on port 64470? If not, wait a few seconds and retry.
WARNING: could not create listen socket for "127.0.0.1"
FATAL: could not create any TCP/IP sockets

(bowerbird, in particular, has a few recent examples)

I think the reason why we're getting "No error" instead of a useful
strerror report is that socket.c doesn't provide an implementation
of bind() that includes TranslateSocketError(). Why is that?

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2016-01-10 18:36:41 Request - repeat value of \pset title during \watch interations
Previous Message Christian Ullrich 2016-01-10 18:08:37 Re: BUG #13854: SSPI authentication failure: wrong realm name used