Re: Upgrade from 8.4 - Mailing list pgsql-admin

From Brett Stauner
Subject Re: Upgrade from 8.4
Date
Msg-id CAGOrRDgmY9XmhHjAKFMkxXxEaifKb4+YBgGYw4Uh+D=+K0NaUQ@mail.gmail.com
Whole thread Raw
In response to Re: Upgrade from 8.4  (Prashanth Ranjalkar <prashant.ranjalkar@gmail.com>)
List pgsql-admin
I recently upgraded from the 8.2 branch to 9.2.  Since mine was so old the only option I had was the dump/restore functionality, but that's really a simple procedure, just potentially time consuming based on your data and computers.  It's also good to look over the release notes between the versions so you can identify parts of your code (if you use things like plpgsql).  Doing a full dump and restore to a new version can point these issues out, and you can properly test your applications and scheduled tasks against your new server before taking the plunge.

Regards,
-Brett


On Thu, Apr 18, 2013 at 6:58 AM, Prashanth Ranjalkar <prashant.ranjalkar@gmail.com> wrote:
Yes, PostgreSQL 9.2 would be an excellent choice; There are various upgrade options available like dump/restore, slony and pg_upgrade where each have their pros and cons. The selection of upgrade method solely depend upon the data size and available downtime. It's strongly recommended to test upgrade method before live implementation.

 
Thanks & Regards,
 
Prashanth Ranjalkar
Database Consultant & Architect


On Thu, Apr 18, 2013 at 4:40 PM, Rajiv Kasera <rajiv.kasera@pinelabs.com> wrote:

I am planning to upgrade my Postgres DB server from v8.4 to a newer version. Should 9.2 be a good choice for upgrading, it has the best features around replication. Also can someone help me with a guide for the upgrade process and rollback process in case anything fails.

 

Thanks,
Rajiv



pgsql-admin by date:

Previous
From: Prashanth Ranjalkar
Date:
Subject: Re: Upgrade from 8.4
Next
From: "Sofer, Yuval"
Date:
Subject: Primary DB stuck becuase of unavailable standby (synchronized streaming) - please help