pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Sachchida Ojha <sojha@secure-elements.com>
Cc: Michael Glaesemann <grzm@seespotcode.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Autovacuum is running forever
Date: Tue, 21 Aug 2007 17:03:25 -0500
Message-ID: <dcc563d10708211503r7058a1f7v73cff44dc3409c1f@mail.gmail.com> (raw)
In-Reply-To: <E099DB9EF394534CBA0F62ED03CF3BBF05FDBF3A@EXVS01.IceMAIL.com>
References: <E099DB9EF394534CBA0F62ED03CF3BBF647F14@EXVS01.IceMAIL.com>
	<E099DB9EF394534CBA0F62ED03CF3BBF05FDBF3A@EXVS01.IceMAIL.com>

On 8/21/07, Sachchida Ojha <sojha@secure-elements.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).

Not really.  but vacuum will just have to run that long again plus
some the next time it starts up.

Again, it's better to run vacuum more often not less often, and keep
the cost_delay high enough that it doesn't interfere with your I/O.
however, that will make it run even longer.



view thread (13+ messages)  latest in thread

Message-ID: <dcc563d10708211503r7058a1f7v73cff44dc3409c1f@mail.gmail.com>
Permalink:  ../dcc563d10708211503r7058a1f7v73cff44dc3409c1f@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10708211503r7058a1f7v73cff44dc3409c1f@mail.gmail.com

 · 

reply

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: scott.marlowe@gmail.com, sojha@secure-elements.com, grzm@seespotcode.net
  Subject: Re: Autovacuum is running forever
  In-Reply-To: <dcc563d10708211503r7058a1f7v73cff44dc3409c1f@mail.gmail.com>

* 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