Date: Fri, 24 Aug 2007 17:08:13 -0400
From: Bill Moran <wmoran@collaborativefusion.com>
To: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Cc: "Kevin Kempter" <kevin@kevinkempterllc.com>,
	"Pgsql performance" <pgsql-performance@postgresql.org>
Subject: Re: significant vacuum issues - looking for suggestions
Message-Id: <20070824170813.72c0f39e.wmoran@collaborativefusion.com>
In-Reply-To: <46CEFEB4.EE98.0025.0@wicourts.gov>
References: <200708241357.23629.kevin@kevinkempterllc.com>
	<46CEFEB4.EE98.0025.0@wicourts.gov>
Organization: Collaborative Fusion
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

In response to "Kevin Grittner" <Kevin.Grittner@wicourts.gov>:

> >>> On Fri, Aug 24, 2007 at  2:57 PM, in message
> <200708241357.23629.kevin@kevinkempterllc.com>, Kevin Kempter
> <kevin@kevinkempterllc.com> wrote: 
> >    c) setup WAL archiving on the 8.1.4 cluster
> > 
> >    d) do a full dump of the 8.1.4 cluster and restore it to the new 8.2.4 
> > cluster
> > 
> >    e) stop the 8.2.4 cluster and bring it up in recovery mode, pointing it 
> > to 
> > the directory where we're archiving the 8.1.4 cluster's WAL segments.
> 
> You can't use these techniques for a major version upgrade.
> Use pg_dump piped to psql.  That will also eliminate all bloat.

If you can't afford any downtime, you may be able to use Slony to
do your upgrade.  However, slony adds overhead, and if this system
is tapped out already, it may not tolerate the additional overhead.

-- 
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran@collaborativefusion.com
Phone: 412-422-3463x4023