| From: | Joel Jacobson <joel(at)trustly(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_stat_activity.waiting_start |
| Date: | 2017-01-07 18:41:31 |
| Message-ID: | CAASwCXdvQgZ-ox_SyYMF5TAJVH-_rW71vthZynS=EMeexN5Giw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jan 7, 2017 at 3:25 AM, Greg Stark <stark(at)mit(dot)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_waiting
View "pg_catalog.pg_stat_waiting"
Column | Type | Modifiers
-----------------+------------------+-----------
wait_event_type | name |
wait_event | name |
waiting_counter | bigint |
waiting_time | double precision |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-01-07 18:57:37 | Re: Replication/backup defaults |
| Previous Message | Bruce Momjian | 2017-01-07 18:35:54 | Re: Shrink volume of default make output |