X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id C67869FA621 for ; Wed, 31 May 2006 19:49:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 89255-03 for ; Wed, 31 May 2006 19:49:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 645EA9FA5EA for ; Wed, 31 May 2006 19:49:11 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4VMn81p023435; Wed, 31 May 2006 18:49:08 -0400 (EDT) To: Chris Browne cc: pgsql-general@postgresql.org Subject: Re: A quick question on CONTRIB package In-reply-to: <604pz5uaw2.fsf@dba2.int.libertyrms.com> References: <1149096921.25526.121.camel@state.g2switchworks.com> <604pz5uaw2.fsf@dba2.int.libertyrms.com> Comments: In-reply-to Chris Browne message dated "Wed, 31 May 2006 17:45:01 -0400" Date: Wed, 31 May 2006 18:49:08 -0400 Message-ID: <23434.1149115748@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/1572 X-Sequence-Number: 96364 Chris Browne writes: > ramakrishna.reddy@indussoft.com ("Ramakrishna Reddy") writes: >> We have very huge databases in many installations and infact have >> plans for upgrading to latest releases. But as we are not very sure >> about the stability of post 7.2.1 versions, refrained from doing >> that. Could you please suggest me which version is the best in terms >> of stability, performance and minimal bugs. We want to upgrade this >> on both our Windows as well as Linux environments. > Well, there are only three versions worth considering: > ... > It all seems to point to 8.1.4 being the best candidate. I'm having a hard time not rolling on the floor laughing at this discussion. If 7.2.1 is your standard of comparison, any of the later branches are super stable ... A more serious point is that 7.2.x to 8.x is a big jump in terms of behavior; there were a lot of not-so-compatible changes in between. Porting their application code first to 7.4 and then to 8.1 might be a good plan in terms of not dealing with too many things at once. I don't suggest moving their production databases twice, just divvying up the work of testing and updating their applications. regards, tom lane