X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 00F16529E1 for ; Mon, 28 Mar 2005 17:22:36 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 95274-04 for ; Mon, 28 Mar 2005 16:22:26 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 366D052A3F for ; Mon, 28 Mar 2005 17:22:25 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j2SGMKSB029332; Mon, 28 Mar 2005 11:22:20 -0500 (EST) To: Scott Marlowe Cc: Tsirkin Evgeny , pgsql-admin@postgresql.org Subject: Re: is postgresql 8 is realy mature In-reply-to: <1112023393.12450.22.camel@state.g2switchworks.com> References: <4247D3E2.5070602@mail.jct.ac.il> <1112023393.12450.22.camel@state.g2switchworks.com> Comments: In-reply-to Scott Marlowe message dated "Mon, 28 Mar 2005 09:23:14 -0600" Date: Mon, 28 Mar 2005 11:22:20 -0500 Message-ID: <29331.1112026940@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/456 X-Sequence-Number: 16954 Scott Marlowe writes: > On Mon, 2005-03-28 at 03:52, Tsirkin Evgeny wrote: >> So the question is if the 8.0.1 is really well tested > 7.4.7 is very stable, and has had about two years shake down time, > counting beta testing. 8.0 is quite a bit newer, and to top it off, > includes a LOT of changes to the basic way it works. Against which you should consider that there are also some bugs fixed from 7.4.* to 8.0 ... so it's not black and white. I suspect for example that Janning Vygen's xlog-overflow problem of this morning is related to a 7.4-specific bug, which we considered too risky to backpatch (the problem is that btree index build kept shared buffers pinned for long periods, and the solution in 8.0 is to do the build in local memory instead... which is rather a major change). So far I've been very pleased with the low defect rate against 8.0. Most of the bugs we have fixed were either in new features, or were pre-existing problems that also occur in 7.4 or even further back. Since 8.0.2 is due out in a week or so, it'd be worth waiting for that before considering going to production, but you should take a hard look at using 8.0.*. regards, tom lane