From: Ray Stell <stellr@cns.vt.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: lock help
Date: Thu, 20 Mar 2008 12:07:12 -0400
Message-ID: <20080320160712.GA8666@cns.vt.edu> (raw)
In-Reply-To: <8832.1206024149@sss.pgh.pa.us>
References: <20080320133637.GA6306@cns.vt.edu>
<8832.1206024149@sss.pgh.pa.us>
On Thu, Mar 20, 2008 at 10:42:29AM -0400, Tom Lane wrote:
> Ray Stell <stellr@cns.vt.edu> writes:
> Define "wedged" --- what's the actual problem?
client queries not returning.
> If it is a locking issue then the pg_locks view might be useful.
duh, I meant to cut and paste the lock info and sent user info
by being in a panic.
ghiza=# select * from pg_locks;
locktype | database | relation | page | tuple | transactionid | classid | objid | objsubid | transaction | pid | mode | granted
---------------+----------+----------+------+-------+---------------+---------+-------+----------+-------------+-------+-----------------+---------
relation | 16384 | 10328 | | | | | | | 15470960 | 30765 | AccessShareLock | t
transactionid | | | | | 15470960 | | | | 15470960 | 30765 | ExclusiveLock | t
(2 rows)
As it turns out this app is distributed across 3 or 4 dbs and it was an oracle
instance that was hung. However, I was ill prepared to eval the state of
the pg db. Is there a good place to focus in the docs on how to evaluate
locking issues.
Thanks.
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-admin@postgresql.org
Cc: stellr@cns.vt.edu, tgl@sss.pgh.pa.us
Subject: Re: lock help
In-Reply-To: <20080320160712.GA8666@cns.vt.edu>
* 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