From 27552ce5405f0435355e62740be64a34b84b6aca Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sat, 27 Jan 2007 01:27:36 +0000
Subject: [PATCH] Update installation wording for an upgrade to state that
dump/restore should not be done, per Peter.
---
doc/src/sgml/installation.sgml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
index 719e9c1fca7..ad707f8bc3a 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.276 2007/01/26 22:52:50 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.277 2007/01/27 01:27:36 momjian Exp $ -->
<chapter id="installation">
<title><![%standalone-include[<productname>PostgreSQL</>]]>
@@ -386,8 +386,8 @@ su - postgres
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 a backup and restore is optional.
- If you wish to avoid the backup/restore, merely skip those steps below.
+ can use your current data files so you should skip the backup and
+ restore steps below because they are unnecessary.
</para>
<procedure>
--
GitLab