Re: Slow after VACUUM, fast after DROP-CREATE INDEX

From: Harald Fuchs <hf0722x(at)protecting(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Slow after VACUUM, fast after DROP-CREATE INDEX
Date: 2004-08-06 14:12:52
Message-ID: pu3c30jqxn.fsf@srv.protecting.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In article <411296B5(dot)6000204(at)superguai(dot)com>,
ruben <ruben20(at)superguai(dot)com> writes:

> 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?

This was necessary in PostgreSQL up to 7.3.x, but 7.4.x is supposed to
fix that. What version are you running?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephan Szabo 2004-08-06 14:43:50 Re: PostgreSQL 7.4.2 allows foreign key violation
Previous Message N. David 2004-08-06 14:00:57 New PHP + PostgreSQL group at Google Groups 2