From: | Scott Carey <scott(at)richrelevance(dot)com> |
---|---|
To: | 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> |
Cc: | "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:04:32 |
Message-ID: | BDFBB77C9E07BE4A984DAAE981D19F9652E316749E@EXVMBX018-1.exch018.msoutlookonline.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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.
-----Original Message-----
From: pgsql-performance-owner(at)postgresql(dot)org [mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of Kevin Grittner
Sent: Monday, January 04, 2010 1:04 PM
To: Madison Kelly; Gary Doades
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] DB is slow until DB is reloaded
Madison Kelly <linux(at)alteeve(dot)com> wrote:
> I've added CLUSTER -> ANALYZE -> VACUUM to my nightly
> routine and dropped the VACUUM FULL call.
The CLUSTER is probably not going to make much difference once
you've eliminated bloat, unless your queries do a lot of searches in
the sequence of the index used. Be sure to run VACUUM ANALYZE as
one statement, not two separate steps.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2010-01-06 01:16:47 | Re: DB is slow until DB is reloaded |
Previous Message | Scott Carey | 2010-01-05 22:32:12 | Re: pg_connect takes 3.0 seconds |