Re: Unknown winsock error 10061
От | Dave Page |
---|---|
Тема | Re: Unknown winsock error 10061 |
Дата | |
Msg-id | 937d27e10907060426v14977d94i59fb5f188964581c@mail.gmail.com обсуждение исходный текст |
Ответ на | Unknown winsock error 10061 (wstrzalka <wstrzalka@gmail.com>) |
Ответы |
Re: Unknown winsock error 10061
Re: Unknown winsock error 10061 |
Список | pgsql-bugs |
On Mon, Jul 6, 2009 at 11:20 AM, wstrzalka<wstrzalka@gmail.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: =A0could not reattach to shared memory (key=3D288, addr=3D02A00000= ): > 487 > 2009-07-06 11:39:45 CESTLOG: =A0could not receive data from client: > Unknown winsock error 10061 > 2009-07-06 11:39:45 CESTLOG: =A0unexpected EOF on client connection > FATAL: =A0could not reattach to shared memory (key=3D288, addr=3D02A00000= ): > 487 > 2009-07-06 11:40:20 CESTLOG: =A0could not receive data from client: > Unknown winsock error 10061 > 2009-07-06 11:40:20 CESTLOG: =A0unexpected EOF on client connection > 2009-07-06 11:40:20 CESTLOG: =A0could not receive data from client: > Unknown winsock error 10061 > 2009-07-06 11:40:20 CESTLOG: =A0unexpected 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? --=20 Dave Page EnterpriseDB UK: http://www.enterprisedb.com
В списке pgsql-bugs по дате отправления: