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

From Matthew T. O'Connor
Subject Re: Avoiding vacuum full on an UPDATE-heavy table
Date
Msg-id 54139.192.154.91.225.1085167360.squirrel@192.154.91.225
Whole thread Raw
In response to Avoiding vacuum full on an UPDATE-heavy table  (Bill Montgomery <billm@lulu.com>)
Responses Re: Avoiding vacuum full on an UPDATE-heavy table
List pgsql-performance
> Is there any way to avoid doing a periodic VACUUM FULL on this table,
> given the fairly radical usage pattern? Or is the (ugly) answer to
> redesign our application to avoid this usage pattern?

Yes, you should be able to doing avoid periodic VACUUM FULL.  The problem
is that your table needs to be vacuumed MUCH more often.  What should
happen is that assuming you have enough FSM space allocated and assuming
you vacuum the "right" amount, your table will reach a steady state size.
As you could see your from you vacumm verbose output your table was almost
entriely dead space.

pg_autovacuum would probably help as it monitors activity and vacuumus
tables accordingly.  It is not included with 7.3.x but if you download it
and compile yourself it will work against a 7.3.x server.

Good luck,

Matthew



pgsql-performance by date:

Previous
From: Neil Conway
Date:
Subject: Re: PostgreSQL caching
Next
From: Marty Scholes
Date:
Subject: Re: PostgreSQL caching