8000 Expect EWOULDBLOCK from a non-blocking connect() call only on Windows. · sqlparser/postgres@a5380bd · GitHub
[go: up one dir, main page]

Skip to content

Commit a5380bd

Browse files
committed
Expect EWOULDBLOCK from a non-blocking connect() call only on Windows.
On Unix-ish platforms, EWOULDBLOCK may be the same as EAGAIN, which is *not* a success return, at least not on Linux. We need to treat it as a failure to avoid giving a misleading error message. Per the Single Unix Spec, only EINPROGRESS and EINTR returns indicate that the connection attempt is in progress. On Windows, on the other hand, EWOULDBLOCK (WSAEWOULDBLOCK) is the expected case. We must accept EINPROGRESS as well because Cygwin will return that, and it doesn't seem worth distinguishing Cygwin from native Windows here. It's not very clear whether EINTR can occur on Windows, but let's leave that part of the logic alone in the absence of concrete trouble reports. Also, remove the test for errno == 0, effectively reverting commit da9501b, which AFAICS was just a thinko; or at best it might have been a workaround for a platform-specific bug, which we can hope is gone now thirteen years later. In any case, since libpq makes no effort to reset errno to zero before calling connect(), it seems unlikely that that test has ever reliably done anything useful. Andres Freund and Tom Lane
1 parent b02b5dc commit a5380bd

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

src/interfaces/libpq/fe-connect.c

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1633,9 +1633,10 @@ PQconnectPoll(PGconn *conn)
16331633
addr_cur->ai_addrlen) < 0)
16341634
{
16351635
if (SOCK_ERRNO == EINPROGRESS ||
1636+
#ifdef WIN32
16361637
SOCK_ERRNO == EWOULDBLOCK ||
1637-
SOCK_ERRNO == EINTR ||
1638-
SOCK_ERRNO == 0)
1638+
#endif
1639+
SOCK_ERRNO == EINTR)
16391640
{
16401641
/*
16411642
* This is fine - we're in non-blocking mode, and

0 commit comments

Comments
 (0)
0