Re: Exhaustive list of what takes what locks

From: Nikolas Everett <nik9000(at)gmail(dot)com>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Exhaustive list of what takes what locks
Date: 2011-02-02 22:12:19
Message-ID: AANLkTimLVnRfZ+jdagwFArBHWijFWWaqyZEitAhscPF7@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, Feb 2, 2011 at 3:29 PM, Nikolas Everett <nik9000(at)gmail(dot)com> wrote:

>
>
> On Wed, Feb 2, 2011 at 2:53 PM, Nikolas Everett <nik9000(at)gmail(dot)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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Dan Birken 2011-02-02 23:15:26 Which RAID Controllers to pick/avoid?
Previous Message Mladen Gogala 2011-02-02 22:03:28 Re: [HACKERS] Slow count(*) again...