From: Iain <iain@mst.co.jp>
To: pgsql-admin@postgresql.org
Subject: Routine maintenance - vacuum, analyse and autovacuum
Date: Thu, 29 Jan 2004 18:59:28 +0900
Message-ID: <000901c3e64e$9611c390$7201a8c0@mst1x5r347kymb> (raw)
Hi All,
I'm supposed to put together a plan for the routine maintenance of the new
database we are building using v7.4, and I have a question or two.
I'm interested in the auto vacuum daemon, but havn't located any good
information about it so far, I'd like to know if people generally recommend
using it or not.
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.
On the other hand, the system is quite busy during the day, and once the
batch processes have finished the system is idle until about 9am.
The system is used 365 days a year, which doesn't leave much opportunity for
VACUUM FULL or unload reloads.
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?
Thanks for your help,
regards
Iain
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: iain@mst.co.jp
Subject: Re: Routine maintenance - vacuum, analyse and autovacuum
In-Reply-To: <000901c3e64e$9611c390$7201a8c0@mst1x5r347kymb>
References: <000901c3e64e$9611c390$7201a8c0@mst1x5r347kymb>
* 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