Re: Dynamic LWLock tracing via pg_stat_lwlock (proof of concept)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, ik(at)postgresql-consulting(dot)com, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Dynamic LWLock tracing via pg_stat_lwlock (proof of concept)
Date: 2014-10-03 15:51:46
Message-ID: CA+TgmoZHLntjH8_DZYA2P4Z18pVZnETUqEH+63rnnkON0AKLhA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 3, 2014 at 11:33 AM, Bruce Momjian <bruce(at)momjian(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2014-10-03 15:53:48 Re: [RFC] Incremental backup v2: add backup profile to base backup
Previous Message Robert Haas 2014-10-03 15:48:07 Re: Typo fixes in src/backend/rewrite/rewriteHandler.c