From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: wiki on monitoring locks has queries that don't seem to work |
Date: | 2013-11-25 20:47:19 |
Message-ID: | CAMkU=1yh6_jDDWboFMvsNTNBdZEvo9zYDYixjh6v6nK+k4pGqQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Nov 25, 2013 at 11:57 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:
> So I'm running 8.4 and go to this
> page:http://wiki.postgresql.org/wiki/Lock_Monitoring
>
> I have a query that is definitely blocked by another query. I run the
> first or third queries, the ones that explicitly say that they're for
> <9.2 and neither produces any output. The third query gives me a list
> of 182 rows, only a few of which are actually locked in any meaningful
> ways.
>
Those queries only find row-level locks, not object-level locks (as
indicated). I suspect that you are blocking on object-level locks. Maybe
you will have better luck with
http://wiki.postgresql.org/wiki/Lock_dependency_information.
>
> Now if I run this query:
>
> select relname,pg_locks.* from pg_class,pg_locks where
> relfilenode=relation and not granted;
>
> I get the one row for the update / insert / delete that is getting blocked.
>
Can you show us that row?
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua Boyd | 2013-11-25 21:07:21 | Re: Easiest way to CREATE EXTENSION when upgrading from 9.0 to 9.2? |
Previous Message | Merlin Moncure | 2013-11-25 20:35:40 | Re: passing tables name into a cursor |