Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 8E1FE2E3ACF for ; Fri, 11 Jan 2008 13:12:37 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 44895-02-5 for ; Fri, 11 Jan 2008 13:12:31 -0400 (AST) Received: from main1.mycybernet.net (main1.mycybernet.net [209.222.63.135]) by postgresql.org (Postfix) with ESMTP id 5D3E22E3B3E for ; Fri, 11 Jan 2008 13:11:56 -0400 (AST) Received: from 227-54-222-209.mycybernet.net ([209.222.54.227] helo=crankycanuck.ca) by main1.mycybernet.net with esmtp (Exim 4.62) (envelope-from ) id 1JDLkb-0006I5-PO for pgsql-admin@postgresql.org; Fri, 11 Jan 2008 10:24:53 -0500 Received: by crankycanuck.ca (Postfix, from userid 1000) id 24E344FFE2; Fri, 11 Jan 2008 10:24:49 -0500 (EST) Date: Fri, 11 Jan 2008 10:24:49 -0500 From: Andrew Sullivan To: pgsql-admin@postgresql.org Subject: Re: Need some info. Message-ID: <20080111152449.GA5963@crankycanuck.ca> Mail-Followup-To: Andrew Sullivan , pgsql-admin@postgresql.org References: <3D5445983859B84B92669C0D883EA6FB0BC38B00@ZENMAILHQ1.ind.zensar.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D5445983859B84B92669C0D883EA6FB0BC38B00@ZENMAILHQ1.ind.zensar.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/121 X-Sequence-Number: 27895 On Thu, Jan 10, 2008 at 01:07:09PM +0530, Suresh Gupta VG wrote: > We are upgrading the pgsql from 7.4.2 to 8.2.5 on Solaris 9 Spark > machine, I had downloaded the sources also. I had gone through the > instalation documents too. I could not find the procedure to rollback > the new version, if the new version does not support our application. This is a difficulty, yes. > 1) Can we do rollback if required after complete installation?? Generally, major releases are binary incompatible. If you find your upgrade fails, you can of course continue to use your old installation (so don't delete your old data directory!). But if you've processed transactions in the new system, they'll be lost to the old installation, and then you're hosed. What you _can_ do, however, is install Slony. You might need to upgrade your 7.4 version to do this -- the version you have is very old, and there are some bugs that might affect Slony (I don't remember). Not to worry -- that shouldn't be a big deal (it's not a dump and restore). But it will require some planning and such. What you do, in this case, is install Slony on 7.4, add the 8.2.x replica, and let it catch up. When it's time to do your upgrade, you do a switchover (not a failover) and cause the 8.2.x to replicate to your 7.4.x installation. Now transactions that happen in 8.2 will also appear in 7.4, and if something blows up, you can switch back. This feature is an explicit design goal of Slony, and Afilias has used it in production, so I can be confident it works. But you need to do a lot of planning and testing. It isn't something to do in a couple days' time. > 3) If we do the installation in the other directory which doesn't > contain old version. Does it solve our problem Sort of; see above. A