Re: Additional LWLOCK_STATS statistics

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Additional LWLOCK_STATS statistics
Date: 2015-09-16 20:08:10
Message-ID: CA+TgmoZDsBZpSzpgLDbEC9scapoL0TwetPk8QuK=Rs5cLM4eKg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 16, 2015 at 10:13 AM, Jesper Pedersen
<jesper(dot)pedersen(at)redhat(dot)com> wrote:
> Doing block_time / block_count basically only shows "main 0" -- its called
> "unassigned:0"; it also shows up in the max exclusive report. Where it is
> coming from is another question, since it shouldn't be in use.

LWLOCK_STATS itself uses that for something, I think.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Berg 2015-09-16 20:10:00 Building storage/lwlocknames.h?
Previous Message Andres Freund 2015-09-16 20:03:50 Re: Reliance on undefined behaviour in << operator