Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group