From: | Joshua Tolley <eggyknap(at)gmail(dot)com> |
---|---|
To: | Michael Justin <michael(dot)justin(at)gmx(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Automatic database monitoring tool for PostgreSQL ... new project |
Date: | 2011-02-01 05:40:22 |
Message-ID: | 4d479ce3.0849960a.7f59.2d03@mx.google.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jan 31, 2011 at 07:28:36PM +0100, Michael Justin wrote:
> While I am still new to PostgreSQL and have real world experience with
> DB2 InterBase and Firebird only I am interested to write a similar tool
> for PostgreSQL.
>
> Maybe there are articles or discussions which help to get an
> introduction to the practical usage of PostgreSQL Statistics Views, like
> typical queries used to identify potential problems? Just to give an
> example: on InterBase and Firebird, long running transactions can cause
> performance problems, and a typical system monitoring task is to find
> the clients or processes with the oldest transactions (older than x
> minutes).
There are several such tools already. That's not to say that writing another
is a bad idea, just that there are lots you could look at for inspiration. One
of the most widely-used is check_postgres, found here:
http://bucardo.org/wiki/Check_postgres
--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com
From | Date | Subject | |
---|---|---|---|
Next Message | AI Rumman | 2011-02-01 06:14:29 | cast problem in Postgresql 9.0.1 |
Previous Message | Scott Marlowe | 2011-02-01 03:52:08 | Re: Why does my DB size differ between Production and DR? (Postgres 8.4) |