| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Scott Carey <scott(at)richrelevance(dot)com> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Madison Kelly <linux(at)alteeve(dot)com>, Gary Doades <gpd(at)gpdnet(dot)co(dot)uk>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: DB is slow until DB is reloaded |
| Date: | 2010-01-06 01:16:47 |
| Message-ID: | 4B43E47F.5010305@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Scott Carey wrote:
> CLUSTER also does *nothing at all* to a table unless you have chosen an index to CLUSTER on. Its not as simple as switching from VACUUM or VACUUM FULL to CLUSTER.
>
> Does CLUSTER also REINDEX? I seem to recall reducing the size of my indexes by REINDEXing after a CLUSTER, but it was a while ago and I could have been mistaken.
AFAIK CLUSTER builds a new copy of the table, and new indexes for it,
then swaps them into the old table and index's place.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-01-06 01:34:01 | Re: query looping? |
| Previous Message | Scott Carey | 2010-01-06 01:04:32 | Re: DB is slow until DB is reloaded |