Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 84086B5DC1B
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Wed, 21 Sep 2011 14:58:00 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 90930-03
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Wed, 21 Sep 2011 17:57:53 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2
Received: from moutng.kundenserver.de (moutng.kundenserver.de
	[212.227.126.187])
	by mail.postgresql.org (Postfix) with ESMTP id 8573DB5DC0A
	for <pgsql-performance@postgresql.org>;
	Wed, 21 Sep 2011 14:57:53 -0300 (ADT)
Received: from [192.168.1.3] (mail.highperformancepostgresql.com
	[71.179.240.8])
	by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis)
	id 0M2oZ4-1ROmv82Pd0-00stzM; Wed, 21 Sep 2011 19:57:52 +0200
Message-ID: <4E7A259F.9060401@2ndQuadrant.com>
Date: Wed, 21 Sep 2011 13:57:51 -0400
From: Greg Smith <greg@2ndQuadrant.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.1.16) Gecko/20110818 Icedove/3.0.11
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Re: : Performance Improvement Strategy
References: 
 <CAFrxt0j5UysgEU8hQxZ_mGbdex8Ev-bGdGsdpOGYYSO-jO24Fw@mail.gmail.com>
	<4E79E091.2030401@peak6.com>	<4E79A6FF0200002500041506@gw.wicourts.gov>
	<CAFrxt0hikCw7=O=v-yyQxvHog=kGZeTTTsgAauY8dktEDzOf0A@mail.gmail.com>
In-Reply-To: 
 <CAFrxt0hikCw7=O=v-yyQxvHog=kGZeTTTsgAauY8dktEDzOf0A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:mwqhwUH01mdSGJoYiSrxF3k/H3jQnea//e3vsjOr6Wk
	UlRaUmqzRgaHQO+Boe2fTtQN6dw7B1Kq65vmqqSmeKxSt7O1Bx
	LkpqZDouEkG9wslIbFs9lr3xVmnfqgatYd3CmW136u4UmycfFm
	qzkpLnon36V5/41XnIzfRmS1YwRyX8d52pDqVtAOTsTidSHMH5
	SkVhXpsT5nGNF90c3/IFP2bfRg/i6nNLbZMgAq84LIROrgyD+T
	dgsu5ydD6i4MOx2OrEYMjSdP5eMUNz6HtuKQIY3miD3/Zg7REd
	Pv+Qwn48y22/jiZFDo4dwGyGW6O3RBYGBIlsOIjE+tLMW9gPIH
	gdBkPivBGmi15WfzuUzQ=
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	RCVD_IN_DNSWL_NONE=-0.0001
X-Spam-Level: 
X-Archive-Number: 201109/335
X-Sequence-Number: 45111

On 09/21/2011 12:13 PM, Venkat Balaji wrote:
> I as a DBA, suggested to perform VACUUM FULL and RE-INDEXING + ANALYZE 
> to ensure that IO performance and Indexing performance would be good


Read http://wiki.postgresql.org/wiki/VACUUM_FULL before you run VACUUM 
FULL.  You probably don't want to do that.  A multi-gigabyte table can 
easily be unavailable for several hours if you execute VACUUM FULL 
against it.  CLUSTER is almost always faster.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support  www.2ndQuadrant.us