| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Kevin Kempter" <kevink(at)consistentstate(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: vacuum monitoring question |
| Date: | 2008-12-24 16:56:29 |
| Message-ID: | dcc563d10812240856n2bd22623jae27129914db27bc@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Dec 24, 2008 at 9:31 AM, Kevin Kempter
<kevink(at)consistentstate(dot)com> wrote:
> Hi All;
>
> I'm working on a vacuum monitor script to alert us when tables start to grow
> out of control per dead space. Initially I excluded the system catalog
> schemas (pg_catalog, pg_toast, etc) however I wonder if maybe I should
> monitor these as well. PLus I'm looking for any input as to specifically
> what to look for - I've calculated a 'fill factor' which shows the average
> page fill as a percentage but I wonder what other metrics may help monitor
> possible problem tables effeciently..
It's a good idea to keep an eye on system catalogs, especially if you
have a fair bit of DDL going on in your usage. I'd take a look at
what the check_postgresql.pl script does. No need to reproduce all
that work on your own.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Kempter | 2008-12-24 19:09:40 | Re: vacuum monitoring question |
| Previous Message | Kevin Kempter | 2008-12-24 16:31:53 | vacuum monitoring question |