Re: serious problems with vacuuming databases

From: Tomas Vondra <tv(at)fuzzy(dot)cz>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: serious problems with vacuuming databases
Date: 2006-04-09 20:37:05
Message-ID: 44397071.80008@fuzzy.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> Probably the indexes are bloated after the vacuum full. I think the
> best way to get rid of the "fat" is to recreate both tables and indexes
> anew. For this the best tool would be to CLUSTER the tables on some
> index, probably the primary key. This will be much faster than
> VACUUMing the tables, and the indexes will be much smaller as result.

I guess you're right. I forgot to mention there are 12 composed indexes
on the largest (and not deleted) table B, having about 14.000.000 rows
and 1 GB of data. I'll try to dump/reload the database ...

t.v.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tomas Vondra 2006-04-09 20:44:51 Re: serious problems with vacuuming databases
Previous Message Tomas Vondra 2006-04-09 20:33:58 Re: serious problems with vacuuming databases