Re: Adding wait events statistics

From: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Adding wait events statistics
Date: 2025-08-01 09:54:59
Message-ID: aIyO86B88HP52gSb@ip-10-97-1-34.eu-west-3.compute.internal
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Wed, Jul 23, 2025 at 11:38:07AM -0400, Robert Haas wrote:
> I think it's probably a mistake to even be thinking about this in
> terms of wait events. It seems very reasonable to want more data about
> what PostgreSQL backends are doing, but I don't really see any reason
> why that should happen to line up with whatever wait events do. For
> instance, if you asked "what information is useful to gather about
> heavyweight locks?" you might say "well, we'd like to know how many
> times we tried to acquire one, and how many of those times we had to
> wait, and how many of those times we waited for longer than
> deadlock_timeout".

I did find this idea interesting, and gave it a stab in [1].

[1]: https://www.postgresql.org/message-id/aIyNxBWFCybgBZBS%40ip-10-97-1-34.eu-west-3.compute.internal

Regards,

--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2025-08-01 10:03:28 Re: C11 / VS 2019
Previous Message Bertrand Drouvot 2025-08-01 09:49:56 Adding locks statistics