Received: from localhost (maia-2.hub.org [200.46.204.187])
	by postgresql.org (Postfix) with ESMTP id 6DAD59FB27B
	for <pgsql-docs-postgresql.org@postgresql.org>;
	Wed, 21 Feb 2007 14:14:06 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024)
	with ESMTP id 10602-09 for <pgsql-docs-postgresql.org@postgresql.org>;
	Wed, 21 Feb 2007 14:13:58 -0400 (AST)
X-Greylist: delayed 00:19:34.656952 by SQLgrey-1.7.4
Received: from vodamail.co.za (mx5.3g.vodacom.co.za [196.207.32.248])
	by postgresql.org (Postfix) with ESMTP id D158E9FB22E
	for <pgsql-docs@postgresql.org>; Wed, 21 Feb 2007 14:13:58 -0400 (AST)
Received: from localhost (localhost [127.0.0.1])
	by mx4.vodamail.co.za (Postfix) with ESMTP id D94284775
	for <pgsql-docs@postgresql.org>; Wed, 21 Feb 2007 19:54:22 +0200 (SAST)
Received: from vodamail.co.za ([127.0.0.1])
	by localhost (mx4.vodamail.co.za [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 27490-04 for <pgsql-docs@postgresql.org>;
	Wed, 21 Feb 2007 19:54:22 +0200 (SAST)
Received: from josh.flame2.flame.co.za (vc-196-207-32-235.3g.vodacom.co.za
	[196.207.32.235])
	by mx4.vodamail.co.za (Postfix) with ESMTP id B4BB64945
	for <pgsql-docs@postgresql.org>; Wed, 21 Feb 2007 19:54:20 +0200 (SAST)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by josh.flame2.flame.co.za (8.13.7/8.13.7) with ESMTP id l1LHqjrD005061
	for <pgsql-docs@postgresql.org>; Wed, 21 Feb 2007 19:53:42 +0200
Subject: Re: should we have a separate page that clearly defines
	what a minor release is and why it's a good idea to keep up with them?
From: Theo Kramer <theo@flame.co.za>
Reply-To: theo@flame.co.za
To: pgsql-docs@postgresql.org
In-Reply-To: <200702211608.l1LG8XP16780@momjian.us>
References: <200702211608.l1LG8XP16780@momjian.us>
Content-Type: text/plain
Organization: Flame Computing Enterprises cc
Date: Wed, 21 Feb 2007 19:52:45 +0200
Message-Id: <1172080365.2996.2.camel@josh>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) 
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at vodamail.co.za
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=1.694 tagged_above=0 required=5 tests=BAYES_50,
	FORGED_RCVD_HELO, RCVD_IN_BL_SPAMCOP_NET
X-Spam-Level: *
X-Archive-Number: 200702/22
X-Sequence-Number: 4153

Could I venture ...

On Wed, 2007-02-21 at 11:08 -0500, Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > Bruce Momjian wrote:
> > > OK, the FAQ now has:
> > >
> > >     <P>The PostgreSQL team makes only bug fixes in minor releases,
> > 
> > I don't think there is a causality between the above and the below.
> > 
> > >     so, for example, upgrading from 7.4.8 to 7.4.9 does not require
> > >     a dump and restore;  merely stop the database server, install
> > >     the updated binaries, and restart the server.</P>
> > 
> > >     <P>All users should upgrade to the most recent minor release as
> > > soon as it is available.  While upgrades always have some risk,
> > > PostgreSQL minor releases fix only common bugs to reduce the risk of
> > > upgrading. The community considers <i>not</i> upgrading more risky
> > > that upgrading.</P>
> > 
> > What is a "common bug"?
> 
> I changed it to "frequently-encountered bugs".

bugs that may compromise the integrity of your data.

> 
> New text:
> 
>     <P>The PostgreSQL team adds only bug fixes to minor releases.  All

<P>The PostgreSQL team only adds bug fixes to minor releases.  All

>     users should upgrade to the most recent minor release as soon as it
>     is available.  While upgrades always have some risk, PostgreSQL minor
>     releases fix only frequently-encountered bugs to reduce the risk of
>     upgrading.  The community considers <i>not</i> upgrading more risky
>     that upgrading.</P>
> 
>     <P>Upgrading to a minor release, e.g. 8.1.5 to 8.1.6, does not does
>     not require a dump and restore; merely stop the database server,
>     install the updated binaries, and restart the server.</P>
> 
-- 
Regards
Theo