DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=Y7kudCrl4DDqvHcPbOpr1v7pu2r+eFt715UHYGaA/oGUV1Fs5igCc55og7QMmkhAxJ
	MWQzzYvXs6LNeK+e7KnZ7fxh8CYzP2FsH3aEu0abXOf4xacqT859aoPQvmRfkiE1awYO
	vCQ9yrrenALjT829veZ2WZ7X/8lVE3c1HMFV8=
MIME-Version: 1.0
In-Reply-To: <4B426823.4040001@2ndquadrant.com>
References: <4B423D22.7040803@alteeve.com>
	<4B424215.70605@pinpointresearch.com> <4B424FF6.40207@alteeve.com>
	<4B4260E6.7050502@pinpointresearch.com> <4B42638B.4000103@alteeve.com>
	<4B426823.4040001@2ndquadrant.com>
Date: Mon, 4 Jan 2010 15:51:37 -0700
Message-ID: <dcc563d11001041451l326c694bp736aa7019cda8d11@mail.gmail.com>
Subject: Re: DB is slow until DB is reloaded
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Greg Smith <greg@2ndquadrant.com>
Cc: Madison Kelly <linux@alteeve.com>,
	Steve Crawford <scrawford@pinpointresearch.com>,
	pgsql-performance@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 4, 2010 at 3:13 PM, Greg Smith <greg@2ndquadrant.com> wrote:
> Madison Kelly wrote:
>>
>> I think for now, I will stick with 8.1, but I will certainly try out you=
r
>> repo edit above on a test machine and see how that works out. I am alway=
s
>> reticent to change something as fundamental as postgres without "good
>> reason". I guess I am a fan of "if it ain't broke...". :)
>
> PostgreSQL has many fundamental limitations that cannot be resolved no
> matter what you do in 8.1 that are fixed in later versions. =A0The defaul=
t
> behavior for the problem you're having has been massively improved by
> updates made in 8.2, 8.3, and 8.4. =A08.1 can certainly be considered bro=
ken
> in regards to its lack of good and automatic VACUUM and ANALYZE behavior,
> and you're just seeing the first round of issues in that area. =A0Every m=
inute
> you spend applying temporary fixes to the fundamental issues is time you
> could be better spending toward upgrading instead.

Also, the HOT updates in 8.3 made a compelling case for us to update,
and if the OP is suffering from table bloat, HOT might help a lot.