Craig,
Thanks. I assume you mean this one?
http://archives.postgresql.org/pgsql-hackers/2009-07/msg01419.php
I'll check with them to see if its okay if we give this a try.
Thanks,
Regina
-----Original Message-----
From: Craig Ringer [mailto:craig@postnewspapers.com.au]
Sent: Tuesday, August 25, 2009 1:56 AM
To: Regina
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #5007: could not reattach to shared memory
On Tue, 2009-08-25 at 05:44 +0000, Regina wrote:
> The following bug has been logged online:
>
> Bug reference: 5007
> Logged by: Regina
> Email address: lr@pcorp.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
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.
> 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.
--
Craig Ringer
