From c120dd263b18adaee01515c9542f583c0ea44074 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Mon, 29 Jan 2007 21:49:17 +0000
Subject: [PATCH] Update wording for minor release upgrades, per Alvaro.
---
doc/src/sgml/installation.sgml | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
index ad707f8bc3a..b07e694fff9 100644
--- a/doc/src/sgml/installation.sgml
+++ b/doc/src/sgml/installation.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.277 2007/01/27 01:27:36 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.278 2007/01/29 21:49:17 momjian Exp $ -->
<chapter id="installation">
<title><![%standalone-include[<productname>PostgreSQL</>]]>
@@ -385,9 +385,10 @@ su - postgres
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.
+ 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>
--
GitLab