| From: | Clemens Schwaighofer <cs(at)tequila(dot)co(dot)jp> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Index cleanup |
| Date: | 2008-05-22 09:22:55 |
| Message-ID: | 48353B6F.9020107@tequila.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
recently I went through some dev dbs just to clean up some unused
tables. What I found out afterwards is that even if you run a vacuum
full analyze it doesn't removed the index data.
So I was left with table size of a view bytes and gigabyte large indexes.
Of course a re-index cleaned that up.
My question now is, is this intended? Should vacuum full not clean out
the indexes if the table for this index is emptied or a lot of data is
removed.
Should that happen after some time? I doubt, because on one of my life
servers a test db had a size of 33MB overall, but an index size of 1.5GB ...
Whats the best way to handles this on a production system. I doubt its
wise to recreate indexes every month or so ...
--
[ Clemens Schwaighofer -----=====:::::~ ]
[ IT Engineer/Manager ]
[ E-Graphics Communications, TEQUILA\ Japan IT Group ]
[ 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN ]
[ Tel: +81-(0)3-3545-7706 Fax: +81-(0)3-3545-7343 ]
[ http://www.tequila.jp ]
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pierre-Yves Strub | 2008-05-22 11:31:55 | Re: Fragments in tsearch2 headline |
| Previous Message | Tom Lane | 2008-05-21 22:14:44 | Re: Fwd: sql_type tinterval not supported by DBD::Pg |