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

Re: Routine maintenance - vacuum, analyse and autovacuum

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Iain" <iain(at)mst(dot)co(dot)jp>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Routine maintenance - vacuum, analyse and autovacuum
Date: 2004-01-29 16:32:29
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
"Iain" <iain(at)mst(dot)co(dot)jp> writes:
> If we use it, can we stop using nightly vacuums? I'd like to do this if
> possible, since the current version (it's a 7.1 db) of the system runs a
> number of batch processes at night (large deletes and large inserts), and
> finishes with a vacuum analyse. The vacuum takes quite a long time and the
> nightly window is gradually getting tighter and tighter.

Just moving from 7.1 to 7.4 should help, since you can start using plain
vacuum (7.1's vacuum is equivalent to vacuum full IIRC).

> If I start a VACUUM FULL, is it ok to interrupt it part way through? I mean,
> is a partially completed vacuum full worth anything, and is there any danger
> in routinely killing it?

It's crash-safe but you may leave your indexes bigger than before :-(

			regards, tom lane

In response to


pgsql-admin by date

Next:From: Chris White (cjwhite)Date: 2004-01-29 17:03:35
Subject: Re: Error seen when vacuuming pg_largeobject table
Previous:From: Rich CullingfordDate: 2004-01-29 16:20:57
Subject: How to use int2vector

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