Re: Dynamic LWLock tracing via pg_stat_lwlock (proof of concept) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Dynamic LWLock tracing via pg_stat_lwlock (proof of concept)
Date
Msg-id CA+TgmoZHLntjH8_DZYA2P4Z18pVZnETUqEH+63rnnkON0AKLhA@mail.gmail.com
Whole thread Raw
In response to Re: Dynamic LWLock tracing via pg_stat_lwlock (proof of concept)  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Dynamic LWLock tracing via pg_stat_lwlock (proof of concept)
Re: Dynamic LWLock tracing via pg_stat_lwlock (proof of concept)
List pgsql-hackers
On Fri, Oct 3, 2014 at 11:33 AM, Bruce Momjian <bruce@momjian.us> wrote:
> I am assuming almost no one cares about the number of locks, but rather
> they care about cummulative lock durations.
>
> I am having trouble seeing any other option that has such a good
> cost/benefit profile.

I do think that the instrumentation data gathered by LWLOCK_STATS is
useful - very useful.

But it does have significant overhead.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Typo fixes in src/backend/rewrite/rewriteHandler.c
Next
From: Heikki Linnakangas
Date:
Subject: Re: [RFC] Incremental backup v2: add backup profile to base backup