Re: reindex/vacuum locking/performance?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: "Matt Clark" <matt(at)ymogen(dot)net>, "Rob Nagler" <nagler(at)bivio(dot)biz>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: reindex/vacuum locking/performance?
Date: 2003-10-03 23:24:03
Message-ID: 200310031624.03933.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Matt Clark 2003-10-03 23:29:55 Re: reindex/vacuum locking/performance?
Previous Message Matt Clark 2003-10-03 23:21:32 Re: reindex/vacuum locking/performance?