Re: [HACKERS] pg_stat_activity.waiting_start - Mailing list pgsql-hackers

From Joel Jacobson
Subject Re: [HACKERS] pg_stat_activity.waiting_start
Date
Msg-id CAASwCXdvQgZ-ox_SyYMF5TAJVH-_rW71vthZynS=EMeexN5Giw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] pg_stat_activity.waiting_start  (Greg Stark <stark@mit.edu>)
Responses Re: [HACKERS] pg_stat_activity.waiting_start  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On Sat, Jan 7, 2017 at 3:25 AM, Greg Stark <stark@mit.edu> wrote:
> What users need to know is in aggregate how much of the time the
> database is spending working on their queries is going into different
> states.

This is a separate feature idea, but I think it's really valuable as well.

Maybe something similar to pg_stat_user_functions?
But instead grouping by wait_event_type, wait_event, and showing
accumulated count and sum of waiting time since last stat reset, just
like the other pg_stat_* views?

Maybe something like this?

\d pg_stat_waitingView "pg_catalog.pg_stat_waiting"  Column        |       Type       | Modifiers
-----------------+------------------+-----------wait_event_type | name             |wait_event      | name
|waiting_counter| bigint           |waiting_time    | double precision |
 



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Shrink volume of default make output
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Replication/backup defaults