Re: measuring lwlock-related latency spikes

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Greg Stark <stark(at)mit(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: measuring lwlock-related latency spikes
Date: 2012-03-31 11:28:03
Message-ID: CA+TgmobF1a0HKdzvSC-HLZ+46+eSHJ0NPOfQwg0Nmy=UnOFDKg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 31, 2012 at 4:53 AM, Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2012-03-31 12:13:06 Re: Odd out of memory problem.
Previous Message Dobes Vandermeer 2012-03-31 10:27:26 Http Frontend implemented using pgsql?