Re: Postgres entering zombie state once a week in production evnvironment

From: Bryce Nesbitt <bryce2(at)obviously(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Cc: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
Subject: Re: Postgres entering zombie state once a week in production evnvironment
Date: 2009-04-14 20:07:37
Message-ID: 49E4ED09.1020202@obviously.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

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....

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Steve Midgley 2009-04-14 20:20:53 Re: changing multiple pk's in one update
Previous Message Mario Splivalo 2009-04-14 13:43:27 Re: ENUM vs DOMAIN vs FKyed loookup table