From: Peter Eisentraut <peter_e@gmx.net>
Date: Thu, 11 Jun 2015 01:34:03 +0000 (-0400)
Subject: doc: Use "connections" instead of "slots" to avoid confusion
X-Git-Tag: REL9_5_ALPHA1~91
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e80f619acf018a9f79dc6188472ac94ba6742ab5;p=postgresql

doc: Use "connections" instead of "slots" to avoid confusion

The text was written before replication slots existed, but now "slot" is
best not used for anything else in the space of replication.
---

diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml
index 07d3a5a1dc..cb8b8a3c49 100644
--- a/doc/src/sgml/ref/pg_basebackup.sgml
+++ b/doc/src/sgml/ref/pg_basebackup.sgml
@@ -313,7 +313,7 @@ PostgreSQL documentation
             Stream the transaction log while the backup is created. This will
             open a second connection to the server and start streaming the
             transaction log in parallel while running the backup. Therefore,
-            it will use up two slots configured by the
+            it will use up two connections configured by the
             <xref linkend="guc-max-wal-senders"> parameter. As long as the
              client can keep up with transaction log received, using this mode
              requires no extra transaction logs to be saved on the master.