Postgres Pro
Downloads
Home   >   mailing lists

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

From Greg Stark
Subject Re: measuring lwlock-related latency spikes
Date
Msg-id CAM-w4HN1TGQgHxZzFEwsfYK6aYj9vW=Mm2knb31BOAyXeEPQAQ@mail.gmail.com
Whole thread Raw
In response to measuring lwlock-related latency spikes  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: measuring lwlock-related latency spikes  (Simon Riggs <simon@2ndQuadrant.com>)
Re: measuring lwlock-related latency spikes  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
On Sat, Mar 31, 2012 at 4:41 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> But I didn't think we were ever supposed to hold content
> locks for that long.

Isn't that lock held while doing visibility checks? What about I/O
waiting for a clog page to be read?

-- 
greg

pgsql-hackers by date:

Previous
From: Gabriele Bartolini
Date:
Subject: Re: Patch pg_is_in_backup()
Next
From: Aidan Van Dyk
Date:
Subject: Re: Http Frontend implemented using pgsql?