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.
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Peter Eisentraut||Date: 2012-03-31 12:13:06|
|Subject: Re: Odd out of memory problem.|
|Previous:||From: Dobes Vandermeer||Date: 2012-03-31 10:27:26|
|Subject: Http Frontend implemented using pgsql?|