BUG #5007: could not reattach to shared memory

From: "Regina" <lr(at)pcorp(dot)us>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5007: could not reattach to shared memory
Date: 2009-08-25 05:44:16
Message-ID: 200908250544.n7P5iGIx033108@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 5007
Logged by: Regina
Email address: lr(at)pcorp(dot)us
PostgreSQL version: 8.3.6
Operating system: Windows 2008 Server Standard
Description: could not reattach to shared memory
Details:

One of our clients is getting the following error in their PostgreSQL 8.3.6
logs in their ASP.NET application. This 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: could not reattach to shared memory (key=232, addr=01DF0000): 487
%t WARNING: worker took too long to start; cancelled

%t LOG: could not receive data from client: Unknown winsock error 10061
%t LOG: unexpected EOF on client connection

In these cases their .NET app returns this error
Exception of type 'System.OutOfMemoryException' was thrown

I've seen errors like this in the PostgreSQL threads and some suggestion
that this may be a bug and that there is a patch for it. I was thinking of
upgrading them to 8.3.7 but don't see any mention of this in the release
notes to know if 8.3.7 will fix this.
I'm going to test their queries outside of their application to rule out the
application and their query as culprits.

Thanks,
Regina

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Craig Ringer 2009-08-25 05:55:40 Re: BUG #5007: could not reattach to shared memory
Previous Message Tom Lane 2009-08-24 23:56:47 Re: BUG #4999: select 'a' < 'A' is true, but should be false . . .