From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | maczniak(at)gmail(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6521: cannot make connection due to "getsockname() failed: Invalid argument" |
Date: | 2012-04-09 14:15:27 |
Message-ID: | CA+TgmoYPGPMyB7W-c_tfEJOLOJdm5=mpFqV=ktNHdYgXaDn7Cw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Mar 6, 2012 at 12:46 AM, <maczniak(at)gmail(dot)com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6521
> Logged by: Jeongho Jeon
> Email address: maczniak(at)gmail(dot)com
> PostgreSQL version: 9.1.1
> Operating system: 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. 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!
Sometimes this sort of issue can be caused by anti-virus software
(even if it's disabled).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-04-09 14:18:28 | Re: corrupted table postgresql 8.3 |
Previous Message | Robert Haas | 2012-04-09 14:10:34 | Re: BUG #6528: pglesslog still referenced in docs, but no 9.1 support |