pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Greg Smith <greg@2ndquadrant.com>
Cc: Madison Kelly <linux@alteeve.com>
Cc: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: DB is slow until DB is reloaded
Date: Mon, 4 Jan 2010 15:51:37 -0700
Message-ID: <dcc563d11001041451l326c694bp736aa7019cda8d11@mail.gmail.com> (raw)
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>

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 your
>> repo edit above on a test machine and see how that works out. I am always
>> 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.  The default
> behavior for the problem you're having has been massively improved by
> updates made in 8.2, 8.3, and 8.4.  8.1 can certainly be considered broken
> 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.  Every minute
> 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.



view thread (25+ messages)  latest in thread

Message-ID: <dcc563d11001041451l326c694bp736aa7019cda8d11@mail.gmail.com>
Permalink:  ../dcc563d11001041451l326c694bp736aa7019cda8d11@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d11001041451l326c694bp736aa7019cda8d11@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: scott.marlowe@gmail.com, greg@2ndquadrant.com, linux@alteeve.com, scrawford@pinpointresearch.com
  Subject: Re: DB is slow until DB is reloaded
  In-Reply-To: <dcc563d11001041451l326c694bp736aa7019cda8d11@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox