Re: Unknown winsock error 10061

From: Dave Page <dpage(at)pgadmin(dot)org>
To: wstrzalka <wstrzalka(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Unknown winsock error 10061
Date: 2009-07-06 11:26:38
Message-ID: 937d27e10907060426v14977d94i59fb5f188964581c@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jul 6, 2009 at 11:20 AM, wstrzalka<wstrzalka(at)gmail(dot)com> wrote:
> After upgrading to 8.4 on Vista I see no progress on the shared memory
> problem unfortunately.
>
> I think it's even worse now (previously it happened mainly when OS
> went to sleep & then was restored, now it's all the time).
>
> My log looks like this.
> ----------------------------------------------------------------------------------------------------------------------------------------------
> FATAL:  could not reattach to shared memory (key=288, addr=02A00000):
> 487
> 2009-07-06 11:39:45 CESTLOG:  could not receive data from client:
> Unknown winsock error 10061
> 2009-07-06 11:39:45 CESTLOG:  unexpected EOF on client connection
> FATAL:  could not reattach to shared memory (key=288, addr=02A00000):
> 487
> 2009-07-06 11:40:20 CESTLOG:  could not receive data from client:
> Unknown winsock error 10061
> 2009-07-06 11:40:20 CESTLOG:  unexpected EOF on client connection
> 2009-07-06 11:40:20 CESTLOG:  could not receive data from client:
> Unknown winsock error 10061
> 2009-07-06 11:40:20 CESTLOG:  unexpected EOF on client connection
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Our application runs on Linux in the production environment, but all
> the developers works on Windows with local PG installations. Some of
> them are getting the error - some don't.
> .
> It's really big problem explaining to the people that PG is really
> good database.
>
> Is there any chance to do something with it?

We'd love to, but noone with Windows development experience and
familiarity with how PostgreSQL works has yet to be able to reproduce
the problem. As you have a some people that are affected and some that
aren't, perhaps you can help figure out what triggers the bug. Can you
tell if there is any distinguishing factor between the two groups?
Maybe installation options chosen, other software that's installed
(particularly anti-virus or firewall packages), windows service pack
level, domain membership, particular hardware?

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jasen Betts 2009-07-06 11:31:21 Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore
Previous Message Dimitri Fontaine 2009-07-06 10:28:59 Re: BUG #4901: Column name "window" breaks pg_dump/pg_restore