Date: Wed, 31 Mar 2010 17:47:57 -0300
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Scott Carey <scott@richrelevance.com>
Cc: Andy Colson <andy@squeakycode.net>, Gnanakumar <gnanam@zoniac.com>,
	"pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Database size growing over time and leads to
 performance impact
Message-ID: <20100331204757.GE3284@alvh.no-ip.org>
References: <004701cacdad$7013e9f0$503bbdd0$@com>
	<4BAE09AE.9020305@squeakycode.net>
	<CB770C9C-F676-4153-8CBF-C698C253DD11@richrelevance.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CB770C9C-F676-4153-8CBF-C698C253DD11@richrelevance.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

Scott Carey wrote:
> 
> On Mar 27, 2010, at 6:35 AM, Andy Colson wrote:
> > 
> > Dont "VACUUM FULL", its not helping you, and is being removed in newer versions.
> > 
> 
> Off topic:  How is that going to work?  CLUSTER doesn't work on tables
> without an index.  I would love to be able to CLUSTER on some column
> set that doesn't necessarily have an index.

VACUUM FULL has been rewritten in 9.0 so that it uses the CLUSTER logic,
except that it doesn't require an index.

If you want to do it in earlier versions, you can use a no-op SET TYPE
command, like so:

ALTER TABLE foo ALTER COLUMN bar SET TYPE baz;

assuming that table foo has a column bar which is already of type baz.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support