Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 4A448B5DBD9 for ; Fri, 5 Aug 2011 00:05:26 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 73337-10 for ; Fri, 5 Aug 2011 03:05:15 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id AE8BCB5D800 for ; Fri, 5 Aug 2011 00:05:11 -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 p753578U021112; Thu, 4 Aug 2011 23:05:08 -0400 (EDT) To: Scott Marlowe cc: Sumeet Jauhar , bnicholson@hp.com, pgsql-performance@postgresql.org Subject: Re: Suspected Postgres Datacorruption In-reply-to: References: Comments: In-reply-to Scott Marlowe message dated "Thu, 04 Aug 2011 20:40:05 -0600" Date: Thu, 04 Aug 2011 23:05:07 -0400 Message-ID: <21111.1312513507@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.704 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-0.804 X-Spam-Level: X-Archive-Number: 201108/88 X-Sequence-Number: 44535 Scott Marlowe writes: > I would upgrade to either 8.2 or 9.0 and here's my reasons. with 8.2 > you still have implicit casts, which your application may depend upon. > Most other changes between 7.4 and 8.2 were pretty small, so if > you've got a lot of implicit casts in your SQL, 8.2 will be the least > painful of the upgrades to late model pgsqls. HOWEVER, 8.2 is getting > pretty old now and performance wise 9.0 will pretty handily beat it. > In terms of stability, there are no reports of any versions after > about 8.1 or 8.2 being particularly unstable, but keep in mind that > support for 8.1 and 8.2 will be ending / may have ended already, so if > you can possibly test against 9.0 and see if it works well enough, > then you should really do so. See: http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy 8.1 is dead already, 8.2 will go off life support this December. So if you're getting involved in a major-version upgrade now, you really owe it to yourself to jump to 8.4 or later. IMO anyway. (FWIW, I know of no reason to think that 8.4->9.0 is a bigger jump than any other major-release bump from the application compatibility standpoint. Scott is correct to identify the removal of some implicit casts-to-text in 8.3 as the single largest pain point we've introduced in recent memory. Personally I'm betting that this will be eclipsed by the shift to standard_conforming_strings=on in 9.1 ...) regards, tom lane