Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 5A9E1B5DC09
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Tue, 20 Sep 2011 14:59:54 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 80319-04
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Tue, 20 Sep 2011 17:59:47 +0000 (UTC)
X-Greylist: delayed 00:08:05.878335 by SQLgrey-1.8.0-rc2
Received: from meteor.mejor.pl (meteor.mejor.pl [88.198.102.195])
	by mail.postgresql.org (Postfix) with ESMTP id 66C5CB5DC00
	for <pgsql-performance@postgresql.org>;
	Tue, 20 Sep 2011 14:59:47 -0300 (ADT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mejor.pl;
	s=cokolwiek;
	h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID;
	bh=wTEbcQAyMjUikvjEf7pJ+TGLkrceLL90jXvA90A6PaU=;
	b=q6c4Km1XEiHrxbToHNLAJWuBatmBkvhtf7pSJSmTFMSZegUF1K5uC/E3BR0RMqJT+lekJZnIZByqrFu5yPDmKXMHvManSKD3DWzwP1VOXbRUMC4AhGLF4NDKidwbkI0F;
Received: from r1.spray.net.pl ([83.143.40.194] helo=[192.168.1.5])
	by meteor.mejor.pl with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256)
	(Exim 4.76) (envelope-from <marcin@mejor.pl>) id 1R64Tp-0003fC-Qd
	for pgsql-performance@postgresql.org; Tue, 20 Sep 2011 19:51:37 +0200
Message-ID: <4E78D2A8.9090709@mejor.pl>
Date: Tue, 20 Sep 2011 19:51:36 +0200
From: =?ISO-8859-2?Q?Marcin_Miros=B3aw?= <marcin@mejor.pl>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pl-PL;
	rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Re: : Performance Improvement Strategy
References: 
 <CAFrxt0j5UysgEU8hQxZ_mGbdex8Ev-bGdGsdpOGYYSO-jO24Fw@mail.gmail.com>
In-Reply-To: 
 <CAFrxt0j5UysgEU8hQxZ_mGbdex8Ev-bGdGsdpOGYYSO-jO24Fw@mail.gmail.com>
X-Enigmail-Version: 1.3.1
OpenPGP: id=04423B81
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-0.287 tagged_above=-10 required=5
	tests=BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347,
	RCVD_IN_SORBS_WEB=0.77, RP_MATCHES_RCVD=-0.504
X-Spam-Level: 
X-Archive-Number: 201109/290
X-Sequence-Number: 45066

W dniu 2011-09-20 18:22, Venkat Balaji pisze:
> Hello Everyone,
> 
> I had  posted  a query in "GENERAL" category, not sure if that was the
> correct category to post.
> 
> Please help me understand how to calculate free space in Tables and
> Indexes even after vacuuming and analyzing is performed.
> 
> What i understand is that, even if we perform VACUUM ANALYZE regularly,
> the free space generated is not filled up.
> 
> I see lot of free spaces or free pages in Tables and Indexes. But, I
> need to give an exact calculation on how much space will be reclaimed
> after VACUUM FULL and RE-INDEXING.
> 
> Is there any standard procedure or process to calculate the same ?

Hello!
I hope this link will be usefull for you :
http://wiki.postgresql.org/wiki/Show_database_bloat
Regards