Re: pre-existing shared memory block is still in use after crashes - Mailing list pgsql-general

From Magnus Hagander
Subject Re: pre-existing shared memory block is still in use after crashes
Date
Msg-id x2o9837222c1005060844lfea5d11dtf8ea3cb7e3b45d24@mail.gmail.com
Whole thread Raw
In response to Re: pre-existing shared memory block is still in use after crashes  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-general
On Thu, May 6, 2010 at 17:42, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> Excerpts from Dave Vitek's message of jue may 06 10:44:34 -0400 2010:
>> Hi all,
>>
>> Yesterday I ran into two backend crashes and then an autovacuum launcher
>> process crash.  The autovacuum log was:
>> LOG:  database system is ready to accept connections
>> LOG:  autovacuum launcher process (PID 3788) was terminated by exception
>> 0xC0000142
>> HINT:  See C include file "ntstatus.h" for a description of the
>> hexadecimal value.
>
> 0xC0000142 is STATUS_DLL_INIT_FAILED
>
> Apparently this can mean insufficient heap space.  I'm not sure if this is a
> surprising thing to get during high load.
>
> Not sure what can we do about it.

Do you know how many processes were running at the time? (both pg
backend processes and processes in general)?



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

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pre-existing shared memory block is still in use after crashes
Next
From: Thom Brown
Date:
Subject: Re: I need to take metadata from a shell script.