Re: 14.4 If You Are Upgrading - Suggested Improvements

Done, patch attached.

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

Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > Updated text:
> >
> >    The internal data storage format typically changes in every major
> >    release of <productname>PostgreSQL</>. Therefore, if you are upgrading
> >    an existing installation that does not have a version number of
> >    <quote>&majorversion;.x</quote>, you must back up and restore your
> >    data.  If you are upgrading from the same major version, the new version
> >    can use your current data files so you should skip the backup and
> >    restore steps below because they are unnecessary.
>
> That's better, but I'd suggest using &majorversion;.x in the last
> sentence as well, instead of "the same major version", because some
> people does not yet grasp that we refer to "major" as the first two
> digits, instead thinking that all "7" versions are compatible, and all
> "8", etc.
>
> --
> Alvaro Herrera                                http://www.CommandPrompt.com/
> The PostgreSQL Company - Command Prompt, Inc.

--
  Bruce Momjian   bruce@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +
Index: doc/src/sgml/installation.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v
retrieving revision 1.277
diff -c -c -r1.277 installation.sgml
*** doc/src/sgml/installation.sgml    27 Jan 2007 01:27:36 -0000    1.277
--- doc/src/sgml/installation.sgml    29 Jan 2007 21:48:05 -0000
***************
*** 385,393 ****
     release of <productname>PostgreSQL</>. Therefore, if you are upgrading
     an existing installation that does not have a version number of
     <quote>&majorversion;.x</quote>, you must back up and restore your
!    data.  If you are upgrading from the same major version, the new version
!    can use your current data files so you should skip the backup and
!    restore steps below because they are unnecessary.
    </para>

    <procedure>
--- 385,394 ----
     release of <productname>PostgreSQL</>. Therefore, if you are upgrading
     an existing installation that does not have a version number of
     <quote>&majorversion;.x</quote>, you must back up and restore your
!    data.  If you are upgrading from <productname>PostgreSQL</>
!    <quote>&majorversion;.x</quote>, the new version can use your current
!    data files so you should skip the backup and restore steps below because
!    they are unnecessary.
    </para>

    <procedure>