pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Iain <iain@mst.co.jp>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Routine maintenance - vacuum, analyse and autovacuum
Date: Mon, 2 Feb 2004 11:07:33 +0900
Message-ID: <004201c3e931$52120d90$7201a8c0@mst1x5r347kymb> (raw)
References: <000901c3e64e$9611c390$7201a8c0@mst1x5r347kymb>
	<23606.1075393949@sss.pgh.pa.us>

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

That old DB server has been running contnuously for 2 years they tell me.
Apparently it is also growing despite nightly vacuums and a stable data set
size (old data is purged dai.ly and monthly). Nightly delete/insert batches
and vacuums are taking longer and longer too. I suspect the vacuum isn't
doing what they think - possibly due to the FSM being at the default, and
possibly due to ghost processes holding old record versions open. It has
been stable nonetheless. Anyway, I'm sure we can do much better in 7.4.

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

OK, that's the kind of thing I wanted to know. Basically, partial runs of
vacuum full are not likely to be of any benefit. So, unless you intend to
let it run to completion, best to avoid it.

Given that our system experiences quite heavy usage during the day, and has
a nightly window for batch processing I'm wondering if the best way to go
about this is to give auto vacuum a miss and just do a standard vacuum after
the batch processes have completed. As long as the FSM is big enough to
handle the amount of data changed in 1 day, it would be OK, right?

Thanks for the input, (and Bruno too)
Iain




view thread (6+ messages)  latest in thread

Message-ID: <004201c3e931$52120d90$7201a8c0@mst1x5r347kymb>
Permalink:  ../004201c3e931$52120d90$7201a8c0@mst1x5r347kymb/
Also on:    postgresql.org/message-id/004201c3e931$52120d90$7201a8c0@mst1x5r347kymb

 · 

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 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, tgl@sss.pgh.pa.us
  Subject: Re: Routine maintenance - vacuum, analyse and autovacuum
  In-Reply-To: <004201c3e931$52120d90$7201a8c0@mst1x5r347kymb>
  References: <000901c3e64e$9611c390$7201a8c0@mst1x5r347kymb> <23606.1075393949@sss.pgh.pa.us> <004201c3e931$52120d90$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