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 20:29:50
Message-ID: AANLkTinpSW8oAr=tKB2Ahfker1a=7CCRXmmyz5cVSdFP@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Mladen Gogala 2011-02-02 20:54:26 Re: [HACKERS] Slow count(*) again...
Previous Message Nikolas Everett 2011-02-02 19:53:49 Re: Exhaustive list of what takes what locks