Re: measuring lwlock-related latency spikes

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)mit(dot)edu>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: measuring lwlock-related latency spikes
Date: 2012-04-02 21:27:56
Message-ID: 899AD279-FBCC-4E0E-95D6-176AA70DEA18@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Apr 2, 2012, at 3:16 PM, Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:
> Agreed, though I think it means the fsync is happening on a filesystem
> that causes a full system fsync. That time is not normal.

It's ext4, which AFAIK does not have that problem.

>

...Robert

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-04-02 23:20:02 Re: new group commit behavior not helping?
Previous Message Robert Haas 2012-04-02 21:25:46 Re: measuring lwlock-related latency spikes