doe sit include monitoring replicas ?
Cheers,
Ben-
On Fri, Oct 7, 2011 at 3:01 PM, Fernando Hevia wrote:
> pgwatch might also be worth taking a look
> at: http://www.cybertec.at/en/postgresql_products/pgwatch-cybertec-enterprise-postgresql-monitor
> Fernando.-
> On Fri, Sep 30, 2011 at 18:29,
pgwatch might also be worth taking a look at:
http://www.cybertec.at/en/postgresql_products/pgwatch-cybertec-enterprise-postgresql-monitor
Fernando.-
On Fri, Sep 30, 2011 at 18:29, Bobby Dewitt wrote:
> EnterpriseDB now has Postgres Enterprise Manager
> (
> http://enterprisedb.com/products-serv
EnterpriseDB now has Postgres Enterprise Manager
(http://enterprisedb.com/products-services-training/products/postgres-enter
prise-manager) that has some of the information that is being asked for.
It has a hot table analysis report that shows the number of scans, rows
read, etc. Since much of the
Looks like this is generally an area that can be targeted by some
businesses. Or an open source enthusiast.
One centre that captures all the information and produces a report
based on it would be a great thing. Especially in cases like mine,
where I have tens of postgresql installations on differen
Hi Tomas,
I will let you know about "check_postgres.pl".
We will explore "pgmonitor" as well.
The other tool we are working on is "pgwatch", we found this very useful.
Thanks
VB
On Wed, Sep 28, 2011 at 5:44 PM, Tomas Vondra wrote:
> On 28 Září 2011, 9:05, Greg Smith wrote:
> > Venkat Balaji
Thanks Greg !
Sorry, I should have put it the other way.
Actually, I am looking for any tool (if exists) which gets me the following
information with one installation or so.
Please see my replies below.
Thanks
VB
On Wed, Sep 28, 2011 at 12:35 PM, Greg Smith wrote:
> Venkat Balaji wrote:
>
>>
On 28 Září 2011, 9:05, Greg Smith wrote:
> Venkat Balaji wrote:
>>
>> 1. Big Full Table Scans
>> 2. Table with high IOs (hot tables)
>> 3. Highly used Indexes
>> 4. Tables undergoing high DMLs with index scans 0 (with unused indexes)
>> 5. Index usage for heap blk hits
>> 6. Tracking Checkpoints
>
Venkat Balaji wrote:
1. Big Full Table Scans
2. Table with high IOs (hot tables)
3. Highly used Indexes
4. Tables undergoing high DMLs with index scans 0 (with unused indexes)
5. Index usage for heap blk hits
6. Tracking Checkpoints
This is fairly easy to collect and analyze. You might take a
Hello Everyone,
I am implementing a PostgreSQL performance monitoring system (to monitor the
below) which would help us understand the database behavior -
1. Big Full Table Scans
2. Table with high IOs (hot tables)
3. Highly used Indexes
4. Tables undergoing high DMLs with index scans 0 (with unu
