Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id E3C392E00CF for ; Thu, 21 Feb 2008 13:55:36 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 58866-03-2 for ; Thu, 21 Feb 2008 13:55:25 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 039762E00CB for ; Thu, 21 Feb 2008 13:55:24 -0400 (AST) 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 m1LHtJ9S012695; Thu, 21 Feb 2008 12:55:19 -0500 (EST) To: "Joshua D. Drake" cc: Carol Walter , pgsql-admin@postgresql.org Subject: Re: Stable Release? In-reply-to: <20080221090609.551f1b19@commandprompt.com> References: <961C8967-4B46-4A78-9C52-CE028FC103B8@indiana.edu> <20080221090609.551f1b19@commandprompt.com> Comments: In-reply-to "Joshua D. Drake" message dated "Thu, 21 Feb 2008 09:06:09 -0800" Date: Thu, 21 Feb 2008 12:55:19 -0500 Message-ID: <12694.1203616519@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/245 X-Sequence-Number: 28319 "Joshua D. Drake" writes: > Carol Walter wrote: >> A colleague told me that the latest stable release of PostgreSQL is >> 8.1.x. I thought it was 8.2.4. What is the latest stable release? >> I thought there was a problem with autovacuum in the earlier >> releases. Can anyone comment? > Sure: > 8.3.0 is current stable release. > 8.2.6 is current 8.2 stable release. > 8.1.11 is current 8.1 stable release. I wouldn't argue with a DBA who takes the position that a new major PG branch isn't "stable" enough for him/her until it's reached the .1 or .2 or so minor release --- that's just saying that you don't want to be a pioneer. But once a branch is past that point, it's probably at least as stable as older branches. If you look at the patch history, an awful lot of bugs go back more than one branch, and there are known issues in old branches that never will be fixed. By now I would certainly consider 8.2.latest as the most stable available release. The correct term for 8.1 and before is not "stable" but "obsolete". The only reason we continue to support them is for the convenience of people who have databases too big for annual dump/reload exercises and/or don't want to re-test their applications that often. regards, tom lane