Slow after VACUUM, fast after DROP-CREATE INDEX - Mailing list pgsql-general

From ruben
Subject Slow after VACUUM, fast after DROP-CREATE INDEX
Date
Msg-id 411296B5.6000204@superguai.com
Whole thread Raw
In response to Re: open of /usr/lib/pgsql/data/pg_clog/0F3E failed  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi:

Lately I run into some problems with postmaster fatal errors, corrupted
data and indexes, lost tuples, etc. I was advised to check hardware,
I'll do so.

Today, one of the processes running daily took 4 hours when it takes
about 5 minutes. After a VACCUM ANALYZE of the affected tables it took
the same to finish, then I recreated (drop and create) the index of the
affected table and the process when again fast. My question is, isn't
enough to run a VACCUM to optimize a table and its indexes? Is it
advisable to recreate indexes from time to time?

Thanks in advance.



pgsql-general by date:

Previous
From: Greg Stark
Date:
Subject: Re: most idiomatic way to "update or insert"?
Next
From: Amir Zicherman
Date:
Subject: getting dead locks with 2 functions