From: | "Sachchida Ojha" <sojha(at)secure-elements(dot)com> |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "Michael Glaesemann" <grzm(at)seespotcode(dot)net>, <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Autovacuum is running forever |
Date: | 2007-08-21 22:07:44 |
Message-ID: | E099DB9EF394534CBA0F62ED03CF3BBF05FDBF5A@EXVS01.IceMAIL.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
We are having only two disk (40GB each). One disk is used for OS, App
Server, and application. Second disk is used for postgresql database.
It's a dual cpu machine having 2 GB of ram.
Regards
Sachchida
-----Original Message-----
From: Scott Marlowe [mailto:scott(dot)marlowe(at)gmail(dot)com]
Sent: Tuesday, August 21, 2007 6:05 PM
To: Sachchida Ojha
Cc: Michael Glaesemann; pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] Autovacuum is running forever
On 8/21/07, Sachchida Ojha <sojha(at)secure-elements(dot)com> wrote:
> Is there any data corruption/damage to the database if we forcefully
> kill autovacuum using cron job (if it is running longer than a
> predefined time frame).
Oh, and I'd look at your I/O subsystem. You might want to look at
putting $300 hardware RAID cards with battery backed cache and 4 or so
disks in a RAID10 in them. It sounds to me like you could use more I/O
for your vacuuming. Vacuuming isn't CPU intensive, but it can be I/O
intensive.
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-08-21 22:19:59 | Re: Autovacuum is running forever |
Previous Message | Scott Marlowe | 2007-08-21 22:05:05 | Re: Autovacuum is running forever |