Hi, Along these lines, the usual upgrade path is a pg_dump/pg_restore set. However, what if your database is large (> 50GB), and you have to minimize your downtime (say less than an hour or two). Any suggestions on how to handle that kind of situation? It sure would be nice to have some kind of tool to update in-place a database, though I know that's not a likely path. Doug -----Original Message----- From: pgsql-performance-owner@xxxxxxxxxxxxxx [mailto:pgsql-performance-owner@xxxxxxxxxxxxxx] On Behalf Of Scott Marlowe Sent: Tuesday, May 13, 2008 4:26 AM To: Gauri Kanekar Cc: pgsql-performance@xxxxxxxxxxxxxx Subject: Re: [PERFORM] Installation Steps to migrate to Postgres 8.3.1 On Mon, May 12, 2008 at 11:40 PM, Gauri Kanekar <meetgaurikanekar@xxxxxxxxx> 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. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
