Received: from localhost (maia-1.hub.org [200.46.204.191])
	by postgresql.org (Postfix) with ESMTP id 6B6B49FB3B3
	for <pgsql-docs-postgresql.org@postgresql.org>;
	Mon, 29 Jan 2007 17:49:41 -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 65833-04 for <pgsql-docs-postgresql.org@postgresql.org>;
	Mon, 29 Jan 2007 17:49:38 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.4
Received: from momjian.us (momjian.us [70.90.9.53])
	by postgresql.org (Postfix) with ESMTP id A1E7A9FB376
	for <pgsql-docs@postgresql.org>; Mon, 29 Jan 2007 17:49:37 -0400 (AST)
Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id
 l0TLna905656;
	Mon, 29 Jan 2007 16:49:36 -0500 (EST)
From: Bruce Momjian <bruce@momjian.us>
Message-Id: <200701292149.l0TLna905656@momjian.us>
Subject: Re: 14.4 If You Are Upgrading - Suggested Improvements
In-Reply-To: <20070129135700.GB14134@alvh.no-ip.org>
To: Alvaro Herrera <alvherre@commandprompt.com>
Date: Mon, 29 Jan 2007 16:49:36 -0500 (EST)
CC: Peter Eisentraut <peter_e@gmx.net>, pgsql-docs@postgresql.org,
	"Thomas F. O'Connell" <tf@o.ptimized.com>
X-Mailer: ELM [version 2.4ME+ PL123]
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="ELM1170107376-29781-1_"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200701/29
X-Sequence-Number: 4125


--ELM1170107376-29781-1_
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"


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

--ELM1170107376-29781-1_
Content-Transfer-Encoding: 7bit
Content-Type: text/x-diff
Content-Disposition: inline; filename="/rtmp/diff"

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>

--ELM1170107376-29781-1_--