On Thu, Mar 20, 2008 at 10:42:29AM -0400, Tom Lane wrote: > Ray Stell <stellr@xxxxxxxxxx> 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. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
