| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Laszlo Nagy <gandalf(at)shopzeus(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Big index sizes |
| Date: | 2008-12-30 09:21:11 |
| Message-ID: | 4959E807.1090107@lelarge.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Laszlo Nagy a écrit :
> We have serveral table where the index size is much bigger than the
> table size.
>
> Example:
>
> select count(*) from product_price -- 2234244
>
> Table size: 400 MB
> Index size: 600 MB
>
> After executing "reindex table product_price", index size reduced to 269MB.
>
> I believe this affects performance.
>
> Vacuuming a table does not rebuild the indexes, am I right?
Neither VACUUM nor VACUUM FULL rebuild the indexes. CLUSTER and REINDEX do.
> I'm not sure
> if I need to do this manually, or is this the result of another problem?
You need to do this manually.
> (For example, too many open transactions, frequent updates?)
>
Regards.
--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anton Bogdanovitch | 2008-12-30 10:41:42 | perform 1 check vs exception when unique_violation |
| Previous Message | Laszlo Nagy | 2008-12-30 09:05:59 | Big index sizes |