Message-ID: <49E4ED09.1020202@obviously.com>
Date: Tue, 14 Apr 2009 13:07:37 -0700
From: Bryce Nesbitt <bryce2@obviously.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
CC: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Subject: Re: Postgres entering zombie state once a week in production
	evnvironment
References: <49E42C72.9070902@obviously.com>
	<200904141026.27567.achill@matrix.gatewaynet.com>
In-Reply-To: <200904141026.27567.achill@matrix.gatewaynet.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Thanks for the thoughts on what to check.   Unfortunately, the priority 
of the people responding to the incidents has been to get the system 
live again.  I will add these items to a list that, hopefully, will be 
run through prior to restarting Postgres.

Achilleas Mantzios wrote:
> Did you check for locks?
> SELECT * from pg_locks;
> SELECT l.locktype,c.relname,l.pid,l.mode from pg_locks l,pg_class c where l.relation=c.oid ;
> Were you able to issue other select commands during the problem? Were you able to start psql and do some simple command?
> Have you ruled out the possibility of the application being locked for other reasons? (limits, network failure,etc....