Re: reindex/vacuum locking/performance? - Mailing list pgsql-performance

From Josh Berkus
Subject Re: reindex/vacuum locking/performance?
Date
Msg-id 200310031624.03933.josh@agliodbs.com
Whole thread Raw
In response to Re: reindex/vacuum locking/performance?  ("Matt Clark" <matt@ymogen.net>)
Responses Re: reindex/vacuum locking/performance?
List pgsql-performance
Rob,

> > I think I need full, because there are updates on the table.  As I
> > understand it, an update in pg is an insert/delete, so it needs
> > to be garbage collected.
>
> Yes and no.  You only need a plain VACUUM that is run often enough to
> recover space as fast as you need to grab it.  For heavily updated tables
> run it often - I run it every 5 minutes on some tables.  A VACUUM FULL is
> only needed if you haven't been running VACUUM often enough in the first
> place.

Also, if you find that you need to run VACUUM FULL often, then you need to
raise your max_fsm_pages.

--
-Josh Berkus
 Aglio Database Solutions
 San Francisco


pgsql-performance by date:

Previous
From: "Matt Clark"
Date:
Subject: Re: reindex/vacuum locking/performance?
Next
From: "Matt Clark"
Date:
Subject: Re: reindex/vacuum locking/performance?