On Wed, Mar 20, 2013 at 6:02 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > I propose that we should add a backend function that simplifies this > type of query. The API that comes to mind is (name subject to > bikeshedding) > > pg_blocking_pids(pid int) returns int[]
I've wanted to use pg_locks as a demonstration for recursive queries many times and ran into the same problem. It's just too hard to figure out which lock holders would be blocking which other locks. I would like to be able to generate the full graph showing indirect blocking. This seems to be not quite powerful enough to do it though. I would have expected something that took whole pg_lock row values or something like that. -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
