Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2422D2E2D9C for ; Thu, 13 Mar 2008 13:04:47 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 06780-07 for ; Thu, 13 Mar 2008 13:04:28 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 12D612E2DAB for ; Thu, 13 Mar 2008 13:04:27 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m2DG4RMR018254; Thu, 13 Mar 2008 12:04:27 -0400 (EDT) To: Geoffrey cc: pgsql-admin@postgresql.org Subject: Re: migration of 7.4 to 8.1 In-reply-to: <47D9313A.4020902@serioustechnology.com> References: <200803122318.00032.xzilla@users.sourceforge.net> <20080312225640.2372f251@commandprompt.com> <47D9313A.4020902@serioustechnology.com> Comments: In-reply-to Geoffrey message dated "Thu, 13 Mar 2008 09:50:50 -0400" Date: Thu, 13 Mar 2008 12:04:27 -0400 Message-ID: <18253.1205424267@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/111 X-Sequence-Number: 28594 Geoffrey writes: > Joshua D. Drake wrote: >> I would avoid 8.3 without extensive testing. 8.2.6 is likely a better >> shot a minimizing one off incompatibilities. > We are in a very similar situation in that we are looking to migrate > from 7.4 to 8.3. So seeing Scott's and Joshua's responses, I'm not sure > if we should go with 8.2 or 8.3. 7.4 to 8.2 isn't exactly a trivial jump either; there are enough incompatibilities that could bite you if you don't test your applications. I don't think JD's argument above holds water. What does hold water is the observation that 8.3 is still at 8.3.0 (though not for much longer) and has certainly got more bugs today than recent 8.2.x releases. That should equalize out by, say, middle of the year. So if you intend to go to production in the next month or two then 8.2.x is a safer bet. If your release timeframe is a bit longer, then 8.3.x would be a good choice because it will perform better and be supported longer. You'd want to be sure you were on 8.3.latest before going live of course. regards, tom lane