Re: BUG #5007: could not reattach to shared memory
От | Magnus Hagander |
---|---|
Тема | Re: BUG #5007: could not reattach to shared memory |
Дата | |
Msg-id | 9837222c0908242317k16c6ea9cgb10ece5f4457585f@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #5007: could not reattach to shared memory (Craig Ringer <craig@postnewspapers.com.au>) |
Список | pgsql-bugs |
On Tuesday, August 25, 2009, Craig Ringer <craig@postnewspapers.com.au> wro= te: > On Tue, 2009-08-25 at 05:44 +0000, Regina wrote: >> The following bug has been logged online: >> >> Bug reference: =A0 =A0 =A05007 >> Logged by: =A0 =A0 =A0 =A0 =A0Regina >> Email address: =A0 =A0 =A0lr@pcorp.us >> PostgreSQL version: 8.3.6 >> Operating system: =A0 Windows 2008 Server Standard >> Description: =A0 =A0 =A0 =A0could not reattach to shared memory >> Details: >> >> One of our clients is getting the following error in their PostgreSQL 8.= 3.6 >> logs in their http://ASP.NET application. =A0This only happens if their = application >> runs a long query (which they dump out to disk and disk size (ESRI >> shapefiles) is generally above 70 mb or more) when this fails. >> >> The error is below: >> FATAL: =A0could not reattach to shared memory (key=3D232, addr=3D01DF000= 0): 487 >> %t WARNING: =A0worker took too long to start; cancelled > > Search the -general mailing list archives for "reattach to shared > memory". The issue has been around for a while but until recently nobody > could reproduce it well enough to isolate it and test possible fixed. > You'll see some recent discussion and a proposed patch. > > Try upgrading to the latest version in the 8.3 series. If you still see > the problem please follow up here, or try the patch for the issuye > proposed on the pgsql-general list. The probable fix is not in a released version - it will be in the next one. Please try to upgrade to the latest and then replace postgres.exe with the one from http://blog.hagander.net ad let us know if it works in your situation. > >> In these cases their .NET app returns this error >> Exception of type 'System.OutOfMemoryException' was thrown > > That's probably a bug in their application caused by failure to properly > handle a connection problem. Yes, or possibly npgsql having the bug, though I haven't heard of it there. The stacktrace should probably tell you where - if not, a memory dump with the debugger. /Magnus --=20 Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
В списке pgsql-bugs по дате отправления: