From: Josh Berkus <josh@agliodbs.com>
To: Matt Clark <matt@ymogen.net>
To: Rob Nagler <nagler@bivio.biz>
To: pgsql-performance@postgresql.org
Subject: Re: reindex/vacuum locking/performance?
Date: Fri, 3 Oct 2003 16:24:03 -0700
Message-ID: <200310031624.03933.josh@agliodbs.com> (raw)
In-Reply-To: <LFEIJBEOKGPDHCEMDGNFMEOBCFAA.matt@ymogen.net>
References: <LFEIJBEOKGPDHCEMDGNFMEOBCFAA.matt@ymogen.net>
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
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, matt@ymogen.net, nagler@bivio.biz
Subject: Re: reindex/vacuum locking/performance?
In-Reply-To: <200310031624.03933.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