Re: RFC: replace pg_stat_activity.waiting with something more descriptive - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: RFC: replace pg_stat_activity.waiting with something more descriptive
Date
Msg-id CAA4eK1LX=VnWChZAisV_-jwngh1MPtR=Lo4yt-RRhexo1U_oUA@mail.gmail.com
Whole thread Raw
In response to Re: RFC: replace pg_stat_activity.waiting with something more descriptive  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: RFC: replace pg_stat_activity.waiting with something more descriptive  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-hackers
On Fri, Mar 4, 2016 at 4:01 PM, Alexander Korotkov <aekorotkov@gmail.com> wrote:
On Fri, Mar 4, 2016 at 7:05 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> I think the wait event types should be documented - and the wait
> events too, perhaps.
>

As discussed upthread, I have added documentation for all the possible wait events and an example.  Some of the LWLocks like AsyncQueueLock and AsyncCtlLock are used for quite similar purpose, so I have kept there explanation as same.

Do you think it worth grouping rows in "wait_event Description" table by wait event type?

They are already grouped (implicitly), do you mean to say that we should add wait event type name as well in that table? If yes, then the only slight worry is that there will lot of repetition in wait_event_type column, otherwise it is okay.


With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: improving GROUP BY estimation
Next
From: Thom Brown
Date:
Subject: Re: RFC: replace pg_stat_activity.waiting with something more descriptive