Skip site navigation (1) Skip section navigation (2)

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: Bruce Momjian <bruce(at)momjian(dot)us>
To: Bruno Wolff III <bruno(at)wolff(dot)to>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>, pgsql-docs(at)postgresql(dot)org
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: 2007-02-23 19:07:23
Message-ID: 200702231907.l1NJ7N716217@momjian.us (view raw or flat)
Thread:
Lists: pgsql-docspgsql-www
I have again updated the FAQ to mention the major/minor release
numbering:

    <H3 id="item3.6">3.6) What is the upgrade process for PostgreSQL?</H3>

    <P>PostgreSQL major releases include new features and occur roughly
    once every year.  A major release is numbered by increasing either
    the first or second part of the version number, e.g. 8.1 to 8.2.

    <P>Major releases usually change the internal format of system tables
    and data files. These changes are often complex, so we don't maintain
    backward compatibility for data files. A dump/reload of the database
    is required for major upgrades.</P>

    <P>Minor releases are numbered by increasing the third part of the
    version number, e.g. 8.1.5 to 8.1.6.  The PostgreSQL team only adds
    bug fixes to minor releases.  All users should upgrade to the most
    recent minor release as soon as possible.  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 riskier than
    upgrading.</P>
`
    <P>Upgrading to a minor release does not does not require a dump and
    restore; merely stop the database server, install the updated binaries,
    and restart the server.</P>



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

Bruno Wolff III wrote:
> On Wed, Feb 21, 2007 at 10:07:22 -0500,
>   Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > 
> >     <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 should change about this text?
> 
> The "soon as available" seems to be too aggressive to me. This seems to
> suggest (to me at least) that these upgrades are so important that you
> might want to skimp on QA to get them in place rapidly. While that may
> sometimes be true, I don't think it is always the case for everybody.

-- 
  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. +

In response to

pgsql-docs by date

Next:From: Bruce MomjianDate: 2007-02-23 20:20:46
Subject: Re: Password issue revisited
Previous:From: Magnus HaganderDate: 2007-02-23 08:33:36
Subject: Re: [DOCS] 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?

pgsql-www by date

Next:From: Dave PageDate: 2007-02-25 05:06:46
Subject: Re: Re: [DOCS] 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?
Previous:From: Joshua D. DrakeDate: 2007-02-23 16:34:53
Subject: Re: [pgsql-advocacy] Deployment Case Study Presentations

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group