Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id C46A61337B56 for ; Tue, 28 Sep 2010 19:46:35 -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 77111-04 for ; Tue, 28 Sep 2010 22:46:29 +0000 (UTC) X-Greylist: delayed 00:31:49.592903 by SQLgrey-1.7.6 Received: from mx02.burntmail.com (mx02.burntmail.com [70.87.63.122]) by mail.postgresql.org (Postfix) with ESMTP id B45C61337B47 for ; Tue, 28 Sep 2010 19:46:28 -0300 (ADT) Received: from [173.79.58.9] (helo=[192.168.1.60]) by mx02.burntmail.com with esmtpa (Exim 4.63) (envelope-from ) id 1P0iRa-0006Wq-Ho for pgsql-performance@postgresql.org; Tue, 28 Sep 2010 17:14:38 -0500 Message-ID: <4CA268CC.8090300@burntmail.com> Date: Tue, 28 Sep 2010 18:14:36 -0400 From: Guy Rouillier User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: Running 9 in production? Sticking with 8.4.4 for a while? References: <4CA253ED.9080403@2ndquadrant.com> In-Reply-To: <4CA253ED.9080403@2ndquadrant.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201009/199 X-Sequence-Number: 40402 On 9/28/2010 4:45 PM, Greg Smith wrote: > Tory M Blue wrote: >> I'm doing an OS upgrade and have been sitting on 8.4.3 for sometime. I >> was wondering if it's better for the short term just to bring things >> to 8.4.4 and let 9.0 bake a bit longer, or are people with large data >> sets running 9.0 in production already? > > I'm aware of two people with large data sets who have been running 9.0 > in production since it was in beta. Like most code, what you have to > consider is how much the code path you expect to use each day has been > modified during the previous release. If you're using 9.0 as "a better > 8.4", the odds of your running into a problem are on the low side of the > risk curve. But those using the features that are both new and were > worked on until the very end of the development cycle, like the new > replication features, they are much more likely to run into a bug. A conservative approach is never to use version x.0 of *anything*. The PG developers are very talented (and also very helpful on these mailing lists - thanks for that), but they are human. For work I'm paid to do (as opposed to my own or charity work), I like to stay at least one point release behind the bleeding edge. -- Guy Rouillier