Re: diagnosing a db crash - server exit code 2 - Mailing list pgsql-admin

From Scott Marlowe
Subject Re: diagnosing a db crash - server exit code 2
Date
Msg-id CAOR=d=3BoU+CRsOLVWY7a870cdQ2uc9KQcBA43cT-5J1_CKhow@mail.gmail.com
Whole thread Raw
In response to Re: diagnosing a db crash - server exit code 2  ("Burgholzer, Robert (DEQ)" <Robert.Burgholzer@deq.virginia.gov>)
List pgsql-admin
On Fri, Sep 23, 2011 at 1:38 PM, Burgholzer, Robert (DEQ)
<Robert.Burgholzer@deq.virginia.gov> wrote:
> Joe,
> Thanks - I will try to check into this - however, we have done some tuning
> on the memory over the last 2 years and gotten it such that it is seldom if
> every having to dip into its swap too substantially -- according to "top",
> we remain under 1% swap usage during most times.   Generally speaking, I run
> 3-5 of these large PHP processes simultaneously with no issue, however, when
> I issue even a "median" function call, after several calls (no consistent
> pattern that I can discern), the backend crashes.
>
> If this were the OOM killer - any way I would diagnose it?

If it's the OOM killer it'll be in your /var/log/messages log.

pgsql-admin by date:

Previous
From: "Burgholzer, Robert (DEQ)"
Date:
Subject: Re: diagnosing a db crash - server exit code 2
Next
From: Joe Conway
Date:
Subject: Re: diagnosing a db crash - server exit code 2