From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tomas Vondra <tv@fuzzy.cz>
Cc: pgsql-performance@postgresql.org
Subject: Re: serious problems with vacuuming databases
Date: Sun, 9 Apr 2006 16:45:55 -0400
Message-ID: <20060409204555.GB16673@surnet.cl> (raw)
In-Reply-To: <44397071.80008@fuzzy.cz>
References: <443950FB.4050707@fuzzy.cz>
<20060409183747.GB15094@surnet.cl>
<44397071.80008@fuzzy.cz>
Tomas Vondra wrote:
> > 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 ...
Huh, I didn't suggest to dump/reload. I suggested CLUSTER. You need to
apply it only to tables where you have lots of dead tuples, which IIRC
are A, C and D.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: alvherre@commandprompt.com, tv@fuzzy.cz
Subject: Re: serious problems with vacuuming databases
In-Reply-To: <20060409204555.GB16673@surnet.cl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox