Skip site navigation (1) Skip section navigation (2)

Re: Autovacuum is running forever

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: (view raw, whole thread or download thread mbox)
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.


-----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

In response to


pgsql-performance by date

Next:From: Scott MarloweDate: 2007-08-21 22:19:59
Subject: Re: Autovacuum is running forever
Previous:From: Scott MarloweDate: 2007-08-21 22:05:05
Subject: Re: Autovacuum is running forever

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group