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 02DFE5294E for ; Tue, 29 Mar 2005 07:13:55 +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 19030-03 for ; Tue, 29 Mar 2005 06:13:45 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 2351353A34 for ; Tue, 29 Mar 2005 07:13:45 +0100 (BST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j2T6Diha020045 for ; Tue, 29 Mar 2005 06:13:44 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j2T5o4ts014229 for pgsql-admin@postgresql.org; Tue, 29 Mar 2005 05:50:04 GMT (envelope-from news) From: Christopher Browne X-Newsgroups: pgsql.admin Subject: Re: is postgresql 8 is realy mature Date: Tue, 29 Mar 2005 00:12:55 -0500 Organization: cbbrowne Computing Inc Lines: 42 Message-ID: References: <4247D3E2.5070602@mail.jct.ac.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Jumbo Shrimp, linux) Cancel-Lock: sha1:jdAC79t9/xmcTCoUZIMLHpVCUwQ= To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200503/460 X-Sequence-Number: 16958 A long time ago, in a galaxy far, far away, tsurkin@mail.jct.ac.il (Tsirkin Evgeny) wrote: > Hi list! > We are using currently postgresql 7.3.4 havily and planning an upgrade. > our choices are either 7.4.x which comes with distribution (suse) or 8.0.1 . > We can allow our selfs some testing time and minor changes in applications > if needed but of course this is good to avoid . > So the question is if the 8.0.1 is really well tested ,or maybe we > should move > to 7.4 or just leave 7.3 where it is? > We wil be thankfull for any sharing of experience . > Thanks. I would certainly seriously consider a move to 7.4.x; that should be a useful improvement in terms of both functionality as well as bug fixes. Version 8.0.1 is a bit less widely used, just yet. Two things about it cause me a bit of pause: 1. Introduction of native Win32 support has "touched" quite a lot of code, with some corresponding potential for diminishing the ability to consider past testing to remain legitimate; 2. The TWO changes in cacheing are pretty major, namely the implementation of ARC, with its forthcoming replacement with 2Q. Tom Lane has observed that there have not been many new defects found, and that of those found, many actually do apply to earlier versions. Which is eminently encouraging. For systems not expected to go into production for a while yet, I'd personally be fairly game to use 8.0.2, once released. For things to "go to production" immediately, I would be more than happy to use a 7.4.6 or 7.4.7; you may fairly reasonably expect to see material improvements with a 7.3->7.4 transition. -- (format nil "~S@~S" "cbbrowne" "gmail.com") http://linuxdatabases.info/info/slony.html Rules of the Evil Overlord #173. "Although it would provide amusement, I will not confess to the hero's rival that I was the one who committed the heinous act for which he blames the hero."