| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> |
| Cc: | PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Index size increases after VACUUM FULL |
| Date: | 2008-09-30 11:19:29 |
| Message-ID: | 48E20B41.8000201@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gurjeet Singh wrote:
> On Tue, Sep 30, 2008 at 3:09 PM, Heikki Linnakangas <
> heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> 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
Yeah, maybe. Want to suggest a wording?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2008-09-30 11:47:53 | Re: Index size increases after VACUUM FULL |
| Previous Message | Heikki Linnakangas | 2008-09-30 11:02:51 | FSM rewrite committed, loose ends |