Horton

Re: measuring lwlock-related latency spikes

Greg Stark <stark@mit.edu>

View thread
From: Greg Stark <stark@mit.edu>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org
Date: 2012-04-02T10:49:59Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add new files to NLS file lists

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