From: Bryce Nesbitt <bryce2@obviously.com>
To: pgsql-sql@postgresql.org
Cc: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Subject: Re: Postgres entering zombie state once a week in production evnvironment
Date: Tue, 14 Apr 2009 13:07:37 -0700
Message-ID: <49E4ED09.1020202@obviously.com> (raw)
In-Reply-To: <200904141026.27567.achill@matrix.gatewaynet.com>
References: <49E42C72.9070902@obviously.com>
<200904141026.27567.achill@matrix.gatewaynet.com>
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....
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: bryce2@obviously.com, achill@matrix.gatewaynet.com
Subject: Re: Postgres entering zombie state once a week in production evnvironment
In-Reply-To: <49E4ED09.1020202@obviously.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox