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

From Greg Stark
Subject Re: measuring lwlock-related latency spikes
Date
Msg-id CAM-w4HMx0uQtPxBxoLedgvwm3ARq5Non1e7ACt+9UWTFsQVREg@mail.gmail.com
Whole thread Raw
In response to Re: measuring lwlock-related latency spikes  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: measuring lwlock-related latency spikes  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Mon, Apr 2, 2012 at 8:15 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> Not true, please refer to code at line 544, as I already indicated.
>
> My understanding of the instrumentation is that the lock acquired at
> line 526 will show as the blocker until we reach line 555, so anything
> in between could be responsible for the wait.

Hm, but then wouldn't the lock acquisition at line 544 be showing up as well?


-- 
greg


pgsql-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Switching to Homebrew as recommended Mac install?
Next
From: Simon Riggs
Date:
Subject: Re: measuring lwlock-related latency spikes