]> granicus.if.org Git - postgresql/commitdiff
doc: Improve "replication slot" index entries
authorPeter Eisentraut <peter_e@gmx.net>
Tue, 22 Apr 2014 19:22:10 +0000 (15:22 -0400)
committerPeter Eisentraut <peter_e@gmx.net>
Tue, 22 Apr 2014 19:22:10 +0000 (15:22 -0400)
Now that we have accumulated two different "replication slot" concepts,
make the index entries consistent.

doc/src/sgml/high-availability.sgml
doc/src/sgml/logicaldecoding.sgml

index 39d7467ddd10a9b0dd7eadd0fda6186ee3b6b239..7bba65154466c7af7b6428058fb15df3ec0f5cd0 100644 (file)
@@ -876,8 +876,9 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass'
 
   <sect2 id="streaming-replication-slots">
    <title>Replication Slots</title>
-   <indexterm zone="high-availability">
-    <primary>Replication Slots</primary>
+   <indexterm>
+    <primary>replication slot</primary>
+    <secondary>streaming replication</secondary>
    </indexterm>
    <para>
     Replication slots provide an automated way to ensure that the master does
index 965b0e111840c1565e5981a3f5ffbbbd5900e65e..9cbd12c416f6d6ba2131c7577985ea96125bcd34 100644 (file)
@@ -183,13 +183,11 @@ CTRL-C
    </sect2>
 
    <sect2>
+    <title>Replication Slots</title>
     <indexterm>
-     <primary>Logical Replication Slot</primary>
-    </indexterm>
-    <indexterm>
-     <primary>Replication Slot</primary>
+     <primary>replication slot</primary>
+     <secondary>logical replication</secondary>
     </indexterm>
-    <title>Replication Slots</title>
     <para>
      In the context of logical replication, a slot represents a stream of
      changes which can be replayed to a client in the order they were made on