Thread: PG fails on Windows Server 2008: could not reattach to shared memory ... : 487

The server intermittently fails on simple queries.
Log full of the above error log.

Does anyone know on which version this problem is fixed?
Or a specific patch?

Thanks

Danny Abraham
BMC Software
CTM&D Business Unit
972-52-4286-513
danny_abraham@bmc.com

I don't believe it's been fixed.  It seems like the folks who hack the
windows port haven't got a reproduceable failure.

On Thu, Aug 6, 2009 at 4:00 AM, Abraham, Danny<danny_abraham@bmc.com> wrote:
> The server intermittently fails on simple queries.
> Log full of the above error log.
>
> Does anyone know on which version this problem is fixed?
> Or a specific patch?
>
> Thanks
>
> Danny Abraham
> BMC Software
> CTM&D Business Unit
> 972-52-4286-513
> danny_abraham@bmc.com
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>



--
When fascism comes to America, it will be intolerance sold as diversity.

On Thu, Aug 6, 2009 at 12:00, Abraham, Danny<danny_abraham@bmc.com> wrote:
> The server intermittently fails on simple queries.
> Log full of the above error log.
>
> Does anyone know on which version this problem is fixed?
> Or a specific patch?

Please see http://blog.hagander.net/archives/149-Help-us-test-a-patch-for-the-Win32-shared-memory-issue.html
for binaries with an experimental patch.


--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

Does anybody have a proven way to regenerate this problem?

SO that I can tell that the patch really does fix it?

Thanks

Danny

Does anybody have a proven way to regenerate this problem?

This way I can decide that the patch does fix it?

Thanks

Danny

On Sun, Aug 9, 2009 at 10:22, Abraham, Danny<danny_abraham@bmc.com> wrote:
> Does anybody have a proven way to regenerate this problem?
>
> SO that I can tell that the patch really does fix it?

No. That's the reason it has taken so long to figure out how to fix it
(which we hopefully have done now).


--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

2010/2/4 Owen Hartnett <owen@clipboardinc.com>:
>
> On Aug 9, 2009, at 3:10 PM, Magnus Hagander wrote:
>
>> On Sun, Aug 9, 2009 at 10:22, Abraham, Danny<danny_abraham@bmc.com> wrote:
>>> Does anybody have a proven way to regenerate this problem?
>>>
>>> SO that I can tell that the patch really does fix it?
>>
>> No. That's the reason it has taken so long to figure out how to fix it
>> (which we hopefully have done now).
>
> Has a consensus been arrived at?  Is this patch rolled into the current system?

The patch is included in the latest versions, yes. I don't recall
seeing any reports of the problem remaining after the patch, but it's
not 100% sure of course.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

On Aug 9, 2009, at 3:10 PM, Magnus Hagander wrote:

> On Sun, Aug 9, 2009 at 10:22, Abraham, Danny<danny_abraham@bmc.com> wrote:
>> Does anybody have a proven way to regenerate this problem?
>>
>> SO that I can tell that the patch really does fix it?
>
> No. That's the reason it has taken so long to figure out how to fix it
> (which we hopefully have done now).

Has a consensus been arrived at?  Is this patch rolled into the current system?

I have a client wants to install W2K8 server release 2 and he's asking if there's any conflict.  I can update him to
thelatest when he does. 

Thanks,

-Owen
>
>
> --
> Magnus Hagander
> Me: http://www.hagander.net/
> Work: http://www.redpill-linpro.com/
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

On Feb 4, 2010, at 3:47 PM, Magnus Hagander wrote:

> 2010/2/4 Owen Hartnett <owen@clipboardinc.com>:
>>
>> On Aug 9, 2009, at 3:10 PM, Magnus Hagander wrote:
>>
>>> On Sun, Aug 9, 2009 at 10:22, Abraham, Danny<danny_abraham@bmc.com> wrote:
>>>> Does anybody have a proven way to regenerate this problem?
>>>>
>>>> SO that I can tell that the patch really does fix it?
>>>
>>> No. That's the reason it has taken so long to figure out how to fix it
>>> (which we hopefully have done now).
>>
>> Has a consensus been arrived at?  Is this patch rolled into the current system?
>
> The patch is included in the latest versions, yes. I don't recall
> seeing any reports of the problem remaining after the patch, but it's
> not 100% sure of course.

Thanks, Magnus, I can see no reason why we shouldn't attempt to migrate to Server 2008 now.

-Owen