From: William Scott Jordan <wsjordan@brownpapertickets.com>
To: pgsql-performance@postgresql.org
Subject: VACUUM vs. REINDEX
Date: Fri, 07 Jul 2006 15:29:19 -0700
Message-ID: <6.2.3.0.2.20060707145857.0342ca58@mail.pandimensional.com> (raw)
Hi all!
Can anyone explain to me what VACUUM does that REINDEX doesn't? We
have a frequently updated table on Postgres 7.4 on FC3 with about
35000 rows which we VACUUM hourly and VACUUM FULL once per day. It
seem like the table still slows to a crawl every few weeks. Running
a REINDEX by itself or a VACUUM FULL by itself doesn't seem to help,
but running a REINDEX followed immediately by a VACUUM FULL seems to
solve the problem.
I'm trying to decide now if we need to include a daily REINDEX along
with our daily VACUUM FULL, and more importantly I'm just curious to
know why we should or shouldn't do that.
Any information on this subject would be appreciated.
-Scott
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: wsjordan@brownpapertickets.com
Subject: Re: VACUUM vs. REINDEX
In-Reply-To: <6.2.3.0.2.20060707145857.0342ca58@mail.pandimensional.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