Re: Avoiding vacuum full on an UPDATE-heavy table - Mailing list pgsql-performance

From Josh Berkus
Subject Re: Avoiding vacuum full on an UPDATE-heavy table
Date
Msg-id 200405241208.50933.josh@agliodbs.com
Whole thread Raw
In response to Re: Avoiding vacuum full on an UPDATE-heavy table  (Bill Montgomery <billm@lulu.com>)
List pgsql-performance
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


pgsql-performance by date:

Previous
From: Josh Berkus
Date:
Subject: Re: index's relpages after table analyzed
Next
From: Litao Wu
Date:
Subject: Re: index's relpages after table analyzed