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?

Updated text:

<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, security, and data corruption
bugs, to reduce the risk of upgrading. The community considers
<i>not</i> upgrading more risky than upgrading.</P>

---------------------------------------------------------------------------

Theo Kramer wrote:
> 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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +