From 61edd524017c4a3fa5f35e72e49f70f058be7a99 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Fri, 26 Jul 2013 13:52:01 -0400
Subject: pg_upgrade docs: don't use cluster for binary/lib In a few cases,
pg_upgrade said old/new cluster location when it meant old/new Postgres
install location, so fix those. Per private email report
---
doc/src/sgml/pgupgrade.sgml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
(limited to 'doc/src')
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 523fe440841..c04e552bc93 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -81,14 +81,14 @@
old_bindir>old_bindir>
- the old cluster executable directory;
+ the old PostgreSQL executable directory;
environment variable PGBINOLD>new_bindir>new_bindir>
- the new cluster executable directory;
+ the new PostgreSQL executable directory;
environment variable PGBINNEW>
@@ -255,7 +255,8 @@ gmake prefix=/usr/local/pgsql.new install
Install the pg_upgrade> binary and
- pg_upgrade_support> library in the new PostgreSQL cluster.
+ pg_upgrade_support> library in the new PostgreSQL
+ installation.
--
cgit v1.2.3