Received: from localhost (maia-1.hub.org [200.46.204.191])
	by postgresql.org (Postfix) with ESMTP id 582E29FBDD6
	for <pgsql-docs-postgresql.org@postgresql.org>;
	Wed, 21 Feb 2007 14:54:16 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024)
	with ESMTP id 82961-07 for <pgsql-docs-postgresql.org@postgresql.org>;
	Wed, 21 Feb 2007 14:54:06 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226])
	by postgresql.org (Postfix) with ESMTP id 4F51E9FBDC7
	for <pgsql-docs@postgresql.org>; Wed, 21 Feb 2007 14:54:06 -0400 (AST)
Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226])
	by svr2.hagander.net (Postfix) with ESMTP id 14FC0DCC5D8;
	Wed, 21 Feb 2007 19:54:05 +0100 (CET)
Received: by svr2.hagander.net (Postfix, from userid 1000)
	id 0FF96DCC5D7; Wed, 21 Feb 2007 19:54:05 +0100 (CET)
Date: Wed, 21 Feb 2007 19:54:05 +0100
From: Magnus Hagander <magnus@hagander.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Peter Eisentraut <peter_e@gmx.net>, pgsql-docs@postgresql.org,
	Andrew Hammond <andrew.george.hammond@gmail.com>
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?
Message-ID: <20070221185405.GB21607@svr2.hagander.net>
References: <200702211642.45668.peter_e@gmx.net>
	<200702211608.l1LG8XP16780@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200702211608.l1LG8XP16780@momjian.us>
User-Agent: Mutt/1.5.11
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.051 tagged_above=0 required=5 tests=AWL, BAYES_50
X-Spam-Level: 
X-Archive-Number: 200702/25
X-Sequence-Number: 4156

On Wed, Feb 21, 2007 at 11:08:33AM -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".
> 
> New text:
> 
>     <P>The PostgreSQL team adds only 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>

I still think this should live somewhere other than the FAQ. (It can
live in the FAQ as well, of course, but..)

I'm not entirely sure about the "frequently-encountered". AFAIK, we fix
serious stability bugs (or security bugs) even if they are fairly hard
to trigger. (it's also good to mention that we do patch security bugs, I
think)

//Magnus