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

From Alexander Korotkov
Subject Re: RFC: replace pg_stat_activity.waiting with something more descriptive
Date
Msg-id CAPpHfduyQAJOvmSBuU-9Uh9=dt0UPMNg8aYWxCV8EDtioaRi-g@mail.gmail.com
Whole thread Raw
In response to Re: RFC: replace pg_stat_activity.waiting with something more descriptive  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: RFC: replace pg_stat_activity.waiting with something more descriptive
List pgsql-hackers
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? It would be nice if user a priori knows which wait event have which type. Readability of this large table will be also improved.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company 

pgsql-hackers by date:

Previous
From: Ildar Musin
Date:
Subject: Re: raw output from copy
Next
From: Tomas Vondra
Date:
Subject: Re: WIP: Upper planner pathification