From: Josh Berkus <josh@agliodbs.com>
To: Bill Montgomery <billm@lulu.com>
To: pgsql-performance@postgresql.org
Subject: Re: Avoiding vacuum full on an UPDATE-heavy table
Date: Mon, 24 May 2004 12:08:50 -0700
Message-ID: <200405241208.50933.josh@agliodbs.com> (raw)
In-Reply-To: <40AE74BD.5050802@lulu.com>
References: <40AE274F.7020800@lulu.com>
<54139.192.154.91.225.1085167360.squirrel@192.154.91.225>
<40AE74BD.5050802@lulu.com>
Bill,
> As a quick fix, since we're upgrading to 7.4.2 in a few weeks anyhow
> (which includes pg_autovacuum), I've simply set up an hourly vacuum on
> this table. It only takes ~4 seconds to execute when kept up on an
> hourly basis. Is there any penalty to vacuuming too frequently, other
> than the time wasted in an unnecessary vacuum operation?
Nope, no penalty other than the I/O and CPU load while vacuuming. If you
have a lot of transactions involving serial writes to many tables, sometimes
you can get into a deadlock situation, which is annoying, but I wouldn't
assume this to be a problem until it crops up.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, billm@lulu.com
Subject: Re: Avoiding vacuum full on an UPDATE-heavy table
In-Reply-To: <200405241208.50933.josh@agliodbs.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