Re: Add LWLock blocker(s) information

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
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-13 00:39:34
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 2020-08-12 16:47:13 -0700, Peter Geoghegan wrote:
> 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
> >
> > can give you results like e.g.
> >
> It seems to have bitrot. Do you have a more recent version of the script?

Attached. Needed one python3 fix, and to be adapted so it works with
futex based semaphores. Seems to work for both sysv and posix semaphores
now, based a very short test.

sudo python3 ./ -x /home/andres/build/postgres/dev-optimize/vpath/src/backend/postgres -f 3|~/src/flamegraph/

Will add a note to the other thread.


Andres Freund

Attachment Content-Type Size text/x-python 4.8 KB
scoff-10.svg image/svg+xml 26.6 KB
scoff-dev.svg image/svg+xml 26.0 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2020-08-13 00:42:33 Re: [HACKERS] Dynamic instrumentation of lwlock wait times (lwlock flamegraphs)
Previous Message Tom Lane 2020-08-12 23:57:29 Re: run pgindent on a regular basis / scripted manner