Received: from localhost (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 9554363307A
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Tue,  5 Jan 2010 00:32:20 -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 89234-05
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Tue,  5 Jan 2010 04:32:09 +0000 (UTC)
X-Greylist: delayed 00:21:41.76724 by SQLgrey-1.7.6
Received: from mail-yx0-f192.google.com (mail-yx0-f192.google.com
	[209.85.210.192])
	by mail.postgresql.org (Postfix) with ESMTP id D81D26324C4
	for <pgsql-performance@postgresql.org>;
	Tue,  5 Jan 2010 00:32:09 -0400 (AST)
Received: by yxe30 with SMTP id 30so18050531yxe.29
	for <pgsql-performance@postgresql.org>;
	Mon, 04 Jan 2010 20:32:08 -0800 (PST)
Received: by 10.150.89.3 with SMTP id m3mr24114462ybb.186.1262664133180;
	Mon, 04 Jan 2010 20:02:13 -0800 (PST)
Received: from ?192.168.1.100? (cpe-76-176-215-35.san.res.rr.com
	[76.176.215.35])
	by mx.google.com with ESMTPS id 35sm7602848yxh.33.2010.01.04.20.02.11
	(version=SSLv3 cipher=RC4-MD5); Mon, 04 Jan 2010 20:02:12 -0800 (PST)
Message-ID: <4B42B9C2.7050303@emolecules.com>
Date: Mon, 04 Jan 2010 20:02:10 -0800
From: Craig James <craig_james@emolecules.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Madison Kelly <linux@alteeve.com>
CC: 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>	 <4B425222.7070905@gpdnet.co.uk>
	<4B425555.6020709@alteeve.com>	
	<1262638856.29852.4.camel@bnicholson-desktop>	
	<4B425E93.1050207@alteeve.com>
	<4B426359.9040601@pinpointresearch.com>	
	<4B426438.40109@alteeve.com>
	<37d451f71001041406i3f5d8d5fte8a29cfbc06998c9@mail.gmail.com>
	<4B428917.3020305@alteeve.com>
In-Reply-To: <4B428917.3020305@alteeve.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=3.189 tagged_above=-10 required=5
	tests=BAYES_50=0.001, FH_DATE_PAST_20XX=3.188
X-Spam-Level: ***
X-Archive-Number: 201001/38
X-Sequence-Number: 36918

+Madison Kelly wrote:
> You are right, autovacuum is not running after all. From your comment, I 
> am wondering if you'd recommend I turn it on or not? If so, given that I 
> doubt I will upgrade any time soon, how would I enable it? I suppose I 
> could google that, but google rarely shares gotcha's. :)

Most of the pain of a Postgres upgrade is the dump/reload step.  But you've already had to do that several times, so why the hesitation to upgrade?  Upgrading Postgres to the latest release, even if you have to do it from the source code, takes almost no time at all compared to the time you've already burned trying to solve this problem.  Do the upgrade, you won't regret it.

Craig