BUG #6521: cannot make connection due to "getsockname() failed: Invalid argument" - Mailing list pgsql-bugs

The following bug has been logged on the website:

Bug reference:      6521
Logged by:          Jeongho Jeon
Email address:      maczniak@gmail.com
PostgreSQL version: 9.1.1
Operating system:   Windows 7
Description:=20=20=20=20=20=20=20=20

Hi!

PostgreSQL 9.1.1.1 does not accept connections from clients sometimes.=20
PostgreSQL is installed by Windows installer and it is started by Windows
service on boot time automatically.  PostgreSQL logs are like below.  My
coworkers encounter these phenomena occasionally.  After restarting the
PostgreSQL service, it works well.  This log entry comes from
src/backend/libpq/pqcomm.c.  I am not certain that this is a bug. I searched
but could not find a clue.  Thanks!

WSAEINVAL - The socket has not been bound to an address with bind, or
ADDR_ANY is specified in bind but connection has not yet occurred.
from MSDN,
http://msdn.microsoft.com/en-us/library/windows/desktop/ms738543(v=3Dvs.85)=
.aspx

EINVAL - namelen is invalid (e.g., is negative).
from Linux getsockname(2) manpage

-----[log begin]-----
2012-03-01 11:33:49 KST LOG:  database system was shut down at 2012-02-29
20:52:02 KST
2012-03-01 11:33:50 KST LOG:  database system is ready to accept
connections
2012-03-01 11:33:50 KST LOG:  autovacuum launcher started
2012-03-01 11:42:24 KST LOG:  could not receive data from client: No
connection could be made because the target machine actively refused it.

=09
2012-03-01 11:42:24 KST LOG:  unexpected EOF on client connection
2012-03-01 11:42:24 KST LOG:  could not receive data from client: No
connection could be made because the target machine actively refused it.

=09
2012-03-01 11:42:24 KST LOG:  unexpected EOF on client connection
2012-03-01 11:42:24 KST LOG:  could not receive data from client: No
connection could be made because the target machine actively refused it.

=09
2012-03-01 11:42:24 KST LOG:  could not receive data from client: No
connection could be made because the target machine actively refused it.

=09
2012-03-01 11:42:24 KST LOG:  unexpected EOF on client connection
2012-03-01 11:42:24 KST LOG:  unexpected EOF on client connection
2012-03-01 11:42:24 KST LOG:  could not receive data from client: No
connection could be made because the target machine actively refused it.

=09
2012-03-01 11:42:24 KST LOG:  unexpected EOF on client connection
2012-03-01 11:42:24 KST LOG:  could not receive data from client: No
connection could be made because the target machine actively refused it.

=09
2012-03-01 11:42:24 KST LOG:  unexpected EOF on client connection
2012-03-01 11:42:24 KST LOG:  could not receive data from client: No
connection could be made because the target machine actively refused it.

=09
2012-03-01 11:42:24 KST LOG:  unexpected EOF on client connection
2012-03-01 11:42:24 KST LOG:  could not receive data from client: No
connection could be made because the target machine actively refused it.

=09
2012-03-01 11:42:24 KST LOG:  unexpected EOF on client connection
2012-03-01 11:42:27 KST LOG:  getsockname() failed: Invalid argument
2012-03-01 11:42:27 KST LOG:  getsockname() failed: Invalid argument
2012-03-01 11:42:27 KST LOG:  getsockname() failed: Invalid argument
2012-03-01 11:42:27 KST LOG:  getsockname() failed: Invalid argument
2012-03-01 11:44:24 KST LOG:  getsockname() failed: Invalid argument
2012-03-01 11:44:24 KST LOG:  getsockname() failed: Invalid argument
2012-03-01 11:44:24 KST LOG:  getsockname() failed: Invalid argument
2012-03-01 11:44:24 KST LOG:  getsockname() failed: Invalid argument
2012-03-01 11:46:00 KST LOG:  getsockname() failed: Invalid argument
2012-03-01 11:46:00 KST LOG:  getsockname() failed: Invalid argument
-----[log end]-----