Re: diagnosing a db crash - server exit code 2

On Fri, Sep 23, 2011 at 1:23 PM, Joe Conway <mail(at)joeconway(dot)com> wrote:
> On 09/23/2011 12:02 PM, Burgholzer, Robert (DEQ) wrote:
>> I am trying to get my head around why I keep getting crashes to my PG
>> 8.3.7 database on CentOS - Linux version 2.6.18-164.el5.  There are 3
>> slightly different (I think) circumstances leading to a crash of the
>> database, all related in some way to long running PHP scripts with
>> intensive activity on PG connections.
>> #1 - execution of an R call via pLR (sometimes this may crash it all by
>> itself)
>> #2 - execution of a postGIS query (possible)
>> #3 - random occurences, all related to the same long running PHP scripts
>>
>> I have read that perhaps hardware and/or system settings may cause
>> this.  I believe the system is running i9 processors, that may be set
>> into some sort of virtual multi-threading mode.  Thanks for any insight
>> you all can give in tracking this down.
>
> Are you maybe getting bitten by the OOM killer?
>
> http://www.postgresql.org/docs/8.3/interactive/kernel-resources.html#AEN22246

If OP needs a duct tape fix, just create a giant swap file and add it
to swap. Unless there are runaway recursive things happening, then
he's gotta fix those.