Message-ID: <4E7CDCA6.6060803@joeconway.com>
Date: Fri, 23 Sep 2011 12:23:18 -0700
From: Joe Conway <mail@joeconway.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.8.0.12) Gecko/20071019 Fedora/1.5.0.12-3.fc6 pango-text
	Thunderbird/1.5.0.12 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: "Burgholzer, Robert (DEQ)" <Robert.Burgholzer@deq.virginia.gov>
CC: pgsql-admin@postgresql.org
Subject: Re: diagnosing a db crash - server exit code 2
References: 
 <B6C40D17104BEF47B1CB85623CDFAC6357BE26@COVMSGCES-EMB13.cov.virginia.gov>
In-Reply-To: 
 <B6C40D17104BEF47B1CB85623CDFAC6357BE26@COVMSGCES-EMB13.cov.virginia.gov>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

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

Joe

-- 
Joe Conway
credativ LLC: http://www.credativ.us
Linux, PostgreSQL, and general Open Source
Training, Service, Consulting, & 24x7 Support