From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | Greg Stark <stark(at)enterprisedb(dot)com> |
Cc: | David Fetter <david(at)fetter(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Pet Peeves? |
Date: | 2009-02-03 21:33:00 |
Message-ID: | Pine.GSO.4.64.0902031620411.1280@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 3 Feb 2009, Greg Stark wrote:
> Notably, there's no indication of which lock wait queue the ungranted
> locks are in. That means to find out what's blocking a lock would
> require comparing every other lock to it and deciding whether it
> conflicts.
The tool I find myself wanting here would parse pg_locks, find everything
that wasn't granted, scan through looking for the source of contention as
you describe, try to look up what any blockers are doing via
pg_stat_activity, then report on its findings. That's not so difficult to
do by hand that I've bothered automating it completely for the occasional
time this pops up.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Verite | 2009-02-03 21:50:14 | Re: LIKE with pattern containing backslash |
Previous Message | Grzegorz Jaśkiewicz | 2009-02-03 21:31:00 | Re: C function question |