| From: | William Scott Jordan <wsjordan(at)brownpapertickets(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | VACUUM vs. REINDEX |
| Date: | 2006-07-07 22:29:19 |
| Message-ID: | 6.2.3.0.2.20060707145857.0342ca58@mail.pandimensional.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Broersma Jr | 2006-07-07 23:15:27 | Re: VACUUM vs. REINDEX |
| Previous Message | Jeff Frost | 2006-07-07 22:05:31 | Re: Opteron/FreeBSD/PostgreSQL performance poor |