Re: Index size increases after VACUUM FULL - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Re: Index size increases after VACUUM FULL
Date
Msg-id 65937bea0809300331n3e49884ah60cbd87981c0c3ea@mail.gmail.com
Whole thread Raw
In response to Re: Index size increases after VACUUM FULL  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Index size increases after VACUUM FULL  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Tue, Sep 30, 2008 at 3:09 PM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:
Gurjeet Singh wrote:
   I noticed something strange today, and thought I should report it. I
vacuumed a database, and as expected, one of the table's size decreased
(other table were VACUUMed individually earlier); but o my astonishment, the
size of the UNIQUE KEY index on one of the columns increased.

That's normal. VACUUM FULL creates new index pointers for the tuples it moves, which can lead to a bigger index. If it bothers, REINDEX will pack the indexes tighter again.

That explains it... and yes, REINDEX did bring the index size back to normal.

Would it make sense to mention this in docs of VACUUM FULL? Either at

http://www.postgresql.org/docs/8.3/static/routine-vacuuming.html

or at

http://www.postgresql.org/docs/8.3/static/sql-vacuum.html

Best regards,



--
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com

EnterpriseDB      http://www.enterprisedb.com

Mail sent from my BlackLaptop device

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Index size increases after VACUUM FULL
Next
From: Heikki Linnakangas
Date:
Subject: FSM rewrite committed, loose ends