From 0ff7ea5d3c6d126ba9fd05ea1845d49e8c0b4fd9 Mon Sep 17 00:00:00 2001
From: Robert Haas <rhaas@postgresql.org>
Date: Mon, 10 Oct 2011 10:15:45 -0400
Subject: [PATCH] Some minor wordsmithing for the cascading replication
documentation.
Per report from Thom Brown.
---
doc/src/sgml/high-availability.sgml | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 8bcdc07a763..86c2729cfd3 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -924,16 +924,17 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
Promoting a cascading standby terminates the immediate downstream replication
connections which it serves. This is because the timeline becomes different
between standbys, and they can no longer continue replication. The
- effected standby(s) may reconnect to reestablish streaming replication.
+ affected standby(s) may reconnect to reestablish streaming replication.
</para>
<para>
To use cascading replication, set up the cascading standby so that it can
- accept replication connections, i.e., set <varname>max_wal_senders</>,
- <varname>hot_standby</> and authentication option (see
- <xref linkend="streaming-replication"> and <xref linkend="hot-standby">).
- Also set <varname>primary_conninfo</> in the downstream standby to point
- to the cascading standby.
+ accept replication connections (that is, set
+ <xref linkend="guc-max-wal-senders"> and <xref linkend="guc-hot-standby">,
+ and configure
+ <link linkend="auth-pg-hba-conf">host-based authentication</link>).
+ You will also need to set <varname>primary_conninfo</> in the downstream
+ standby to point to the cascading standby.
</para>
</sect2>
--
GitLab