Re: LWLOCK_STATS - Mailing list pgsql-hackers

From Tom Lane
Subject Re: LWLOCK_STATS
Date
Msg-id 19785.1325956703@sss.pgh.pa.us
Whole thread Raw
In response to Re: LWLOCK_STATS  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: LWLOCK_STATS  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> A couple of weeks ago I wrote a little patch that's similar to 
> LWLOCK_STATS, but it prints out % of wallclock time that is spent 
> acquiring, releasing, or waiting for a lock. I find that more useful 
> than the counters.

I would think that the measurement overhead required to obtain two
wall-clock values for every LWLock touch would be so high as to render
any results from this quite suspect.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pgsphere
Next
From: Tom Lane
Date:
Subject: Re: Intermittent regression test failures from index-only plan changes