From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
---|---|
To: | Rafael Martinez <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Need to run CLUSTER to keep performance |
Date: | 2007-11-08 15:09:55 |
Message-ID: | 473326C3.3070206@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Rafael Martinez wrote:
> Heikki Linnakangas wrote:
>> On a small table like that you could run VACUUM every few minutes
>> without much impact on performance. That should keep the table size in
>> check.
>
> Ok, we run VACUUM ANALYZE only one time a day, every night. But we would
> espect the performance to get ok again after running vacuum, and it
> doesn't. Only CLUSTER helps.
If the table is already bloated, a VACUUM won't usually shrink it. It
only makes the space available for reuse, but a sequential scan still
needs to go through a lot of pages.
CLUSTER on the other hand repacks the tuples and gets rid of all the
unused space on pages. You need to run CLUSTER or VACUUM FULL once to
shrink the relation, but after that frequent-enough VACUUMs should keep
the table size down.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Rafael Martinez | 2007-11-08 15:10:10 | Re: Need to run CLUSTER to keep performance |
Previous Message | Tom Lane | 2007-11-08 15:01:09 | Re: Estimation problem with a LIKE clause containing a / |