Re: DB is slow until DB is reloaded - Mailing list pgsql-performance

From Scott Carey
Subject Re: DB is slow until DB is reloaded
Date
Msg-id BDFBB77C9E07BE4A984DAAE981D19F9652E316749E@EXVMBX018-1.exch018.msoutlookonline.net
Whole thread Raw
In response to Re: DB is slow until DB is reloaded  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: DB is slow until DB is reloaded
List 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
switchingfrom 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
whileago and I could have been mistaken. 

-----Original Message-----
From: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Kevin
Grittner
Sent: Monday, January 04, 2010 1:04 PM
To: Madison Kelly; Gary Doades
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] DB is slow until DB is reloaded

Madison Kelly <linux@alteeve.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

--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

pgsql-performance by date:

Previous
From: Scott Carey
Date:
Subject: Re: pg_connect takes 3.0 seconds
Next
From: Craig Ringer
Date:
Subject: Re: DB is slow until DB is reloaded