"Closed connection unexpectedly caused by winsock error 10061 on Win2008 R2

From: Pavel Golub <pavel(at)microolap(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: "Closed connection unexpectedly caused by winsock error 10061 on Win2008 R2
Date: 2014-11-21 08:07:12
Message-ID: 1344463425.20141121100712@gf.microolap.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello, PostgreSQL-development.

This week our support had two complains on a very similar situation.
After several minutes of work clients got "server closed the
connection unexpectedly. This probably means the server terminated
abnormally before or while precessing the request."

One client's environment uses MS Windows Server 2008 R2 and the other
one uses Windows 7.

In the log there are plenty of
"unrecognized winsock error 10061"

Googling gave me some more results on this, e.g.
http://forums.enterprisedb.com/posts/list/3331.page

Do we aware of such cases? Do we have any straight solutions for them?

I've attached the log. It's in German I think.

--
With best wishes,
Pavel mailto:pavel(at)gf(dot)microolap(dot)com

Attachment Content-Type Size
postgresql.log application/octet-stream 300.3 KB

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2014-11-21 08:12:14 Automatic PG_PRINTF_ATTRIBUTE
Previous Message Amit Kapila 2014-11-21 07:20:44 Re: alternative model for handling locking in parallel groups