Received: from localhost (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 134C563307A
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Mon,  4 Jan 2010 16:39:27 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024)
	with ESMTP id 97890-08
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Mon,  4 Jan 2010 20:39:12 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from ppsw-0.csi.cam.ac.uk (ppsw-0.csi.cam.ac.uk [131.111.8.130])
	by mail.postgresql.org (Postfix) with ESMTP id 68C4F632A4F
	for <pgsql-performance@postgresql.org>;
	Mon,  4 Jan 2010 16:39:16 -0400 (AST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from pip.srcf.societies.cam.ac.uk ([131.111.179.83]:47874
	helo=[127.0.0.1])
	by ppsw-0.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.130]:25)
	with esmtp id 1NRthp-0006Cx-2L (Exim 4.70)
	(return-path <rn214@cam.ac.uk>); Mon, 04 Jan 2010 20:39:13 +0000
Message-ID: <4B4251F1.9060700@cam.ac.uk>
Date: Mon, 04 Jan 2010 20:39:13 +0000
From: Richard Neill <rn214@cam.ac.uk>
Organization: RUO3.org
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: Madison Kelly <linux@alteeve.com>
CC: Steve Crawford <scrawford@pinpointresearch.com>,
	pgsql-performance@postgresql.org
Subject: Re: DB is slow until DB is reloaded
References: <4B423D22.7040803@alteeve.com>
	<4B424215.70605@pinpointresearch.com> <4B424FF6.40207@alteeve.com>
In-Reply-To: <4B424FF6.40207@alteeve.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.728 tagged_above=-10 required=5 tests=AWL=-2.461,
	BAYES_50=0.001, FH_DATE_PAST_20XX=3.188
X-Spam-Level: 
X-Archive-Number: 201001/11
X-Sequence-Number: 36891


> Yup, I even tried manually running 'VACUUM FULL' and it didn't help. As 
> for upgrading;

VACUUM FULL is usually considered a bad idea. What you probably want to 
do instead is CLUSTER, followed by ANALYZE.

Basically, VACUUM makes the indexes smaller (but doesn't reclaim much 
space from the tables themselves). VACUUM FULL reclaims space from the 
tables, but bloats the indexes.

> a) I am trying to find a way around the dump/reload. I am doing it as a 
> "last resort" only.
> b) I want to keep the version in CentOS' repo.
> 

Postgres is pretty easy to build from source. It's nicely 
self-contained, and won't bite you with dependency hell. So don't be too 
wary of compiling it.

Richard