From 5691de6c95836e0cef3a2fbb3ce61ce80ddecc69 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 26 Jul 2013 13:52:01 -0400
Subject: [PATCH] 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(-)

diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 8eb0375502..f6cd9f0d88 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -81,14 +81,14 @@
      <varlistentry>
       <term><option>-b</option> <replaceable>bindir</></term>
       <term><option>--old-bindir=</option><replaceable>bindir</></term>
-      <listitem><para>the old cluster executable directory;
+      <listitem><para>the old PostgreSQL executable directory;
       environment variable <envar>PGBINOLD</></para></listitem>
      </varlistentry>
 
      <varlistentry>
       <term><option>-B</option> <replaceable>bindir</></term>
       <term><option>--new-bindir=</option><replaceable>bindir</></term>
-      <listitem><para>the new cluster executable directory;
+      <listitem><para>the new PostgreSQL executable directory;
       environment variable <envar>PGBINNEW</></para></listitem>
      </varlistentry>
 
@@ -254,7 +254,8 @@ gmake prefix=/usr/local/pgsql.new install
 
     <para>
      Install the <application>pg_upgrade</> binary and
-     <application>pg_upgrade_support</> library in the new PostgreSQL cluster.
+     <application>pg_upgrade_support</> library in the new PostgreSQL
+     installation.
     </para>
    </step>
 
-- 
GitLab