Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Big index sizes
- 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: Tue, 30 Dec 2008 10:21:11 +0100
- Message-id: <4959E807.1090107@lelarge.info> <text/plain>
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
- Follow-Ups:
- Re: Big index sizes
- From: Tom Lane
- Re: Big index sizes
- References:
- Big index sizes
- From: Laszlo Nagy
- Big index sizes
- Prev by Date: Big index sizes
- Next by Date: perform 1 check vs exception when unique_violation
- Previous by thread: Big index sizes
- Next by thread: Re: Big index sizes
- Indexes: