Slow after VACUUM, fast after DROP-CREATE INDEX

From: ruben <ruben20(at)superguai(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Slow after VACUUM, fast after DROP-CREATE INDEX
Date: 2004-08-05 20:21:09
Message-ID: 411296B5.6000204@superguai.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Oscar Tuscon 2004-08-05 20:22:13 Re: Sequence Question DOH!
Previous Message Ron St-Pierre 2004-08-05 20:13:47 Re: most idiomatic way to "update or insert"?