| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Ildus Kurbangaliev <i(dot)kurbangaliev(at)postgrespro(dot)ru>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | Re: Waits monitoring |
| Date: | 2015-09-04 22:44:21 |
| Message-ID: | CANP8+j+z9921+yt__hA3rZrH+TNaOwG7qvFEZpTjoBzstZ=wUA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9 July 2015 at 21:10, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
wrote:
> I see that patch of Robert and Amit adds current lock type
> into PgBackendStatus and, in turn, adds it into pg_stat_activity. This is
> small part of what you implement in waits monitoring patch. Dividing big
> features into small pieces makes it much easier to include PostgreSQL. I
> think you should join work of Robert and Amit in inclusion current lock
> type into PgBackendStatus. There are things you could help them to improve.
> And then you can rebase waits monitoring patch according to it.
>
I see the need for both current wait information and for cumulative
historical detail.
I'm willing to wait before reviewing this, but not for more than 1 more CF.
Andres, please decide whether we should punt to next CF now, based upon
other developments. Thanks
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ozgun Erdogan | 2015-09-04 22:52:49 | Re: Horizontal scalability/sharding |
| Previous Message | Simon Riggs | 2015-09-04 22:35:42 | Re: Freeze avoidance of very large table. |