Re: measuring lwlock-related latency spikes - Mailing list pgsql-hackers

From Robert Haas
Subject Re: measuring lwlock-related latency spikes
Date
Msg-id CA+TgmobF1a0HKdzvSC-HLZ+46+eSHJ0NPOfQwg0Nmy=UnOFDKg@mail.gmail.com
Whole thread Raw
In response to Re: measuring lwlock-related latency spikes  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Sat, Mar 31, 2012 at 4:53 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> The next logical step in measuring lock waits is to track the reason
> for the lock wait, not just the lock wait itself.

I had the same thought.  I'm not immediately sure what the best way to
do that is, but I'll see if I can figure something out.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Dobes Vandermeer
Date:
Subject: Http Frontend implemented using pgsql?
Next
From: Peter Eisentraut
Date:
Subject: Re: Odd out of memory problem.