Re: Exhaustive list of what takes what locks - Mailing list pgsql-performance

From Nikolas Everett
Subject Re: Exhaustive list of what takes what locks
Date
Msg-id AANLkTimLVnRfZ+jdagwFArBHWijFWWaqyZEitAhscPF7@mail.gmail.com
Whole thread Raw
In response to Re: Exhaustive list of what takes what locks  (Nikolas Everett <nik9000@gmail.com>)
List pgsql-performance
On Wed, Feb 2, 2011 at 3:29 PM, Nikolas Everett <nik9000@gmail.com> wrote:


On Wed, Feb 2, 2011 at 2:53 PM, Nikolas Everett <nik9000@gmail.com> wrote:
Given that the a list would be difficult to maintain, is there some way I can make Postgres spit out the list of what locks are taken?

--Nik

I just answered my own question -
compile with -DLOCK_DEBUG in your src/Makefile.custom and then SET TRACK_LOCKS=true when you want it.

--Nik 

I just wrote a script to parse the output of postgres' log file into something more useful to me.  I'm not sure that it is right but it certainly seems to be working.

I shoved the script here in case it is useful to anyone:  https://github.com/nik9000/Postgres-Tools

pgsql-performance by date:

Previous
From: Mladen Gogala
Date:
Subject: Re: [HACKERS] Slow count(*) again...
Next
From: Dan Birken
Date:
Subject: Which RAID Controllers to pick/avoid?