| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Dave Vitek <dvitek(at)grammatech(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pre-existing shared memory block is still in use after crashes |
| Date: | 2010-05-06 15:42:36 |
| Message-ID: | 1273160162-sup-8176@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
As for the failed restart, maybe the code that detects a conflicting shared
memory block could use a retry loop somewhere.
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-05-06 15:44:43 | Re: pre-existing shared memory block is still in use after crashes |
| Previous Message | Leif Biberg Kristensen | 2010-05-06 15:37:52 | Re: Need a help in regexp |