DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=lXuaHGLN1brIhqI5ipr/iu2nUESzys3cPC7/ne/7wBLzRvl1ZeV4VGOTMbr7s77+4VBLfcQDk5v5H8IrBOGr8Ivx2l6W9X/qTvSOjkp09ExTD7KnvrQ70m0czjTtjRRSTBSqdO0aYx8bHPCLidDhgXpEW8oGaLWDs3iWurZdDT8=
Message-ID: <dcc563d10805130125hcea33a1x39cd9f3ee81b0687@mail.gmail.com>
Date: Tue, 13 May 2008 02:25:44 -0600
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "Gauri Kanekar" <meetgaurikanekar@gmail.com>
Subject: Re: Installation Steps to migrate to Postgres 8.3.1
Cc: pgsql-performance@postgresql.org
In-Reply-To: <7e4ba9550805122240j7ed6a494hfc10a8b08dad073e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <7e4ba9550805122240j7ed6a494hfc10a8b08dad073e@mail.gmail.com>

On Mon, May 12, 2008 at 11:40 PM, Gauri Kanekar
<meetgaurikanekar@gmail.com> wrote:
> Hi,
>
> We want to migrate from postgres 8.1.3 to postgres 8.3.1.
> Can anybody list out the installation steps to be followed for migration.
> Do we require to take care of something specially.

First, I'd recommend updating your 8.1.x install to 8.1.11 or whatever
the latest is right now.

There are some ugly bugs hiding in 8.1.3 if I remember correctly (Tom
just mentioned one that could do things like leaving orphaned objects
in the db in another thread.)  It's always a good idea to keep up to
date on the updates of pgsql.  Some updates aren't critical, but most
early ones in the 7.x through 8.1 tended to have a lot of bugs fixed
in them in the first few updates.

Then, your migration to 8.3.x can be done a bit more leisurely and
well planned and tested, without putting your current data in danger.