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

From Robert Haas
Subject Re: BUG #6521: cannot make connection due to "getsockname() failed: Invalid argument"
Date
Msg-id CA+TgmoYPGPMyB7W-c_tfEJOLOJdm5=mpFqV=ktNHdYgXaDn7Cw@mail.gmail.com
Whole thread Raw
In response to BUG #6521: cannot make connection due to "getsockname() failed: Invalid argument"  (maczniak@gmail.com)
List pgsql-bugs
On Tue, Mar 6, 2012 at 12:46 AM,  <maczniak@gmail.com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: =A0 =A0 =A06521
> Logged by: =A0 =A0 =A0 =A0 =A0Jeongho Jeon
> Email address: =A0 =A0 =A0maczniak@gmail.com
> PostgreSQL version: 9.1.1
> Operating system: =A0 Windows 7
> Description:
>
> Hi!
>
> PostgreSQL 9.1.1.1 does not accept connections from clients sometimes.
> PostgreSQL is installed by Windows installer and it is started by Windows
> service on boot time automatically. =A0PostgreSQL logs are like below. =
=A0My
> coworkers encounter these phenomena occasionally. =A0After restarting the
> PostgreSQL service, it works well. =A0This log entry comes from
> src/backend/libpq/pqcomm.c. =A0I am not certain that this is a bug. I sea=
rched
> but could not find a clue. =A0Thanks!

Sometimes this sort of issue can be caused by anti-virus software
(even if it's disabled).

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: BUG #6528: pglesslog still referenced in docs, but no 9.1 support
Next
From: Robert Haas
Date:
Subject: Re: corrupted table postgresql 8.3