From: Kieren Scott <kierenscott@hotmail.com>
To: bnichols@ca.afilias.info
To: pgsql-admin@postgresql.org
Subject: Re: Persistent server stats collection
Date: Thu, 26 Aug 2010 15:06:30 +0000
Message-ID: <BAY149-w527FE5E6957EAE67A25CD2AE850@phx.gbl> (raw)
In-Reply-To: <4C766B1D.5010805@ca.afilias.info>
References: <BAY149-w32FC3A294C463F1FA190B3AE850@phx.gbl>
<4C766B1D.5010805@ca.afilias.info>
Thanks Brad. Just installed it on a test database and it's all up and running, looks good.
Date: Thu, 26 Aug 2010 09:24:45 -0400
From: bnichols@ca.afilias.info
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Persistent server stats collection
On 10-08-26 05:15 AM, Kieren Scott wrote:
Hi,
I'm interested in finding a way of gathering and retaining system
statistics in my
postgres instances, so I can see how certain things are changing
over time. I know
postgres provides a range of pre-defined views for viewing current
activity, but are
there any modules/scripts that are available to help capture (on a
scheduled basis)
and retain necessary server stats in tables?
Thanks in advance.
http://pgfoundry.org/projects/pgstatspack/
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
=
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: kierenscott@hotmail.com, bnichols@ca.afilias.info
Subject: Re: Persistent server stats collection
In-Reply-To: <BAY149-w527FE5E6957EAE67A25CD2AE850@phx.gbl>
References: <BAY149-w32FC3A294C463F1FA190B3AE850@phx.gbl> <4C766B1D.5010805@ca.afilias.info> <BAY149-w527FE5E6957EAE67A25CD2AE850@phx.gbl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox