Re: Waits monitoring

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
Cc: Ildus Kurbangaliev <i(dot)kurbangaliev(at)postgrespro(dot)ru>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Waits monitoring
Date: 2015-07-09 14:18:38
Message-ID: CAHGQGwFJrasq4PZm=9xcPcDMfD=ODR3rye5OKZkV8SBK0pd+-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 9, 2015 at 2:12 PM, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> wrote:
> On Thu, Jul 9, 2015 at 1:52 AM, Ildus Kurbangaliev
> <i(dot)kurbangaliev(at)postgrespro(dot)ru> wrote:
>> Hello.
>>
>> Currently, PostgreSQL offers many metrics for monitoring. However, detailed
>> monitoring of waits is still not supported yet. Such monitoring would
>> let dba know how long backend waited for particular event and therefore
>> identify
>> bottlenecks. This functionality is very useful, especially for highload
>> databases. Metric for waits monitoring are provided by many popular
>> commercial
>> DBMS. We currently have requests of this feature from companies migrating to
>> PostgreSQL from commercial DBMS. Thus, I think it would be nice for
>> PostgreSQL
>> to have it too.
>
> Yes, It is good have such wait monitoring views in PostgreSQL.
> you can add this patch to the open commitfest.

Robert and Amit proposed very similar idea and its patch is now being
reviewed in the current CommitFest. So I think that you should attend
that discussion rather than starting new one.

http://www.postgresql.org/message-id/CA+TgmoYd3GTz2_mJfUHF+RPe-bCy75ytJeKVv9x-o+SonCGApw@mail.gmail.com

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-07-09 14:26:49 Re: Re: [HACKERS] GSoC 2015 proposal: Improve the performance of “ALTER TABLE .. SET LOGGED / UNLOGGED” statement
Previous Message Fabrízio de Royes Mello 2015-07-09 14:18:06 Re: [HACKERS] Re: [HACKERS] GSoC 2015 proposal: Improve the performance of “ALTER TABLE .. SET LOGGED / UNLOGGED” statement