public inbox for [email protected]
help / color / mirror / Atom feedFrom: Theo Kramer <[email protected]>
To: [email protected]
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?
Date: Wed, 21 Feb 2007 19:52:45 +0200
Message-ID: <1172080365.2996.2.camel@josh> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
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
view thread (32+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
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?
In-Reply-To: <1172080365.2996.2.camel@josh>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox