Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 85D292E02B6 for ; Thu, 13 Mar 2008 13:17:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 97304-02 for ; Thu, 13 Mar 2008 13:17:23 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by postgresql.org (Postfix) with ESMTP id 3C0C62E014C for ; Thu, 13 Mar 2008 13:17:24 -0300 (ADT) Received: from [172.16.255.106] (66-23-211-34.clients.speedfactory.net [66.23.211.34]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MKpCa-1JZq7M0Aft-0007BW; Thu, 13 Mar 2008 12:17:21 -0400 Message-ID: <47D9538E.8070504@serioustechnology.com> Date: Thu, 13 Mar 2008 12:17:18 -0400 From: Geoffrey User-Agent: Thunderbird 1.5.0.12 (X11/20080213) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: migration of 7.4 to 8.1 References: <200803122318.00032.xzilla@users.sourceforge.net> <20080312225640.2372f251@commandprompt.com> <47D9313A.4020902@serioustechnology.com> <18253.1205424267@sss.pgh.pa.us> In-Reply-To: <18253.1205424267@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1/RJlGYkxbObke+CdShxw9PbvFFQxJkNr++qwp cg5RQ/PluO1kGkt4FH20lgkPvEpSsgwkh6TIdqCC5fmCHjlfST UV715rhqgybIRf/52IfPTKw7ILzmqsI X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/112 X-Sequence-Number: 28595 Tom Lane wrote: > 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. Thanks Tom, that's the kind of feedback I was looking for. We know we've got quite a bit of testing ahead of us with our move to 8.3, so I suspect that by the time we go live, it will be 8.3.1 or more. -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin