Re: Add LWLock blocker(s) information

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add LWLock blocker(s) information
Date: 2020-08-12 23:47:13
Message-ID: CAH2-WzmuM0XsFobQomJguCQ5TERFTNwbfjkZgCpJCc8v8ZFiGQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 10, 2020 at 5:41 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Most of the cases where this kind of information really is interesting
> seem to benefit a lot from having stack information available. That
> obviously has overhead, so we don't want the cost all the
> time. The script at
> https://postgr.es/m/20170622210845.d2hsbqv6rxu2tiye%40alap3.anarazel.de
> can give you results like e.g.
> https://anarazel.de/t/2017-06-22/pgsemwait_64_async.svg

It seems to have bitrot. Do you have a more recent version of the script?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2020-08-12 23:52:42 Re: Switch to multi-inserts for pg_depend
Previous Message Tom Lane 2020-08-12 23:47:01 Re: run pgindent on a regular basis / scripted manner