Reconfigure failover/replication doc items to be varlist entries, rather

than new sections, so they appear all on the same web page.

doc/src/sgml/failover.sgml

@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/failover.sgml,v 1.7 2006/11/16 18:25:58 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/failover.sgml,v 1.8 2006/11/16 21:43:33 momjian Exp $ -->
 
 <chapter id="failover">
  <title>Failover, Replication, Load Balancing, and Clustering Options</title>
@@ -76,8 +76,11 @@
   and load balancing solutions.
  </para>
 
- <sect1 id="shared-disk-failover">
-  <title>Shared Disk Failover</title>
+ <variablelist>
+
+ <varlistentry>
+  <term>Shared Disk Failover</term>
+  <listitem>
 
    <para>
     Shared disk failover avoids synchronization overhead by having only one
@@ -93,10 +96,12 @@
     fails or becomes corrupt, the primary and backup servers are both
     nonfunctional.
    </para>
- </sect1>
+  </listitem>
+ </varlistentry>
 
- <sect1 id="warm-standby-using-point-in-time-recovery">
-  <title>Warm Standby Using Point-In-Time Recovery</title>
+ <varlistentry>
+  <term>Warm Standby Using Point-In-Time Recovery</term>
+  <listitem>
 
    <para>
     A warm standby server (see <xref linkend="warm-standby">) can
@@ -106,10 +111,12 @@
     made the new master database server.  This is asynchronous and
     can only be done for the entire database server.
    </para>
- </sect1>
+  </listitem>
+ </varlistentry>
 
- <sect1 id="continuously-running-replication-server">
-  <title>Continuously Running Replication Server</title>
+ <varlistentry>
+  <term>Continuously Running Replication Server</term>
+  <listitem>
 
    <para>
     A continuously running replication server allows the backup server to
@@ -124,10 +131,12 @@
     granularity.  It updates the backup server in batches, so the replication
     is asynchronous and might lose data during a fail over.
    </para>
- </sect1>
+  </listitem>
+ </varlistentry>
 
- <sect1 id="data-partitioning">
-  <title>Data Partitioning</title>
+ <varlistentry>
+  <term>Data Partitioning</term>
+  <listitem>
 
    <para>
     Data partitioning splits tables into data sets.  Each set can
@@ -135,11 +144,10 @@
     partitioned by offices, e.g. London and Paris.  While London
     and Paris servers have all data records, only London can modify
     London records, and Paris can only modify Paris records.  This
-   is similar to section <xref
-   linkend="continuously-running-replication-server"> above, except
-   that instead of having a read/write server and a read-only server,
-   each server has a read/write data set and a read-only data
-   set.
+    is similar to the "Continuously Running Replication Server"
+    item above, except that instead of having a read/write server
+    and a read-only server, each server has a read/write data set
+    and a read-only data set.
    </para>
 
    <para>
@@ -160,10 +168,12 @@
     tables, London and Paris can be placed in separate tables, and
     inheritance can be used to access both tables using a single table name.
    </para>
- </sect1>
+  </listitem>
+ </varlistentry>
 
- <sect1 id="query-broadcast-load-balancing">
-  <title>Query Broadcast Load Balancing</title>
+ <varlistentry>
+  <term>Query Broadcast Load Balancing</term>
+  <listitem>
 
    <para>
     Query broadcast load balancing is accomplished by having a
@@ -186,10 +196,12 @@
     care must be taken that all transactions either commit or abort
     on all servers  Pgpool is an example of this type of replication.
    </para>
- </sect1>
+  </listitem>
+ </varlistentry>
 
- <sect1 id="clustering-for-load-balancing">
-  <title>Clustering For Load Balancing</title>
+ <varlistentry>
+  <term>Clustering For Load Balancing</term>
+  <listitem>
 
     <para>
     In clustering, each server can accept write requests, and modified
@@ -213,10 +225,12 @@
     linkend="sql-commit-prepared" endterm="sql-commit-prepared-title">)
     can be used to implement this in application code or middleware.
    </para>
- </sect1>
+  </listitem>
+ </varlistentry>
 
- <sect1 id="clustering-for-parallel-query-execution">
-  <title>Clustering For Parallel Query Execution</title>
+ <varlistentry>
+  <term>Clustering For Parallel Query Execution</term>
+  <listitem>
 
    <para>
     This allows multiple servers to work concurrently on a single
@@ -226,10 +240,12 @@
     and returned to the user.  There currently is no
     <productname>PostgreSQL</> open source solution for this.
    </para>
- </sect1>
+  </listitem>
+ </varlistentry>
 
- <sect1 id="commercial-solutions">
-  <title>Commercial Solutions</title>
+ <varlistentry>
+  <term>Commercial Solutions</term>
+  <listitem>
 
    <para>
     Because <productname>PostgreSQL</> is open source and easily
@@ -237,6 +253,9 @@
     and created commercial closed-source solutions with unique
     failover, replication, and load balancing capabilities.
    </para>
- </sect1>
+  </listitem>
+ </varlistentry>
+
+ </variablelist>
 
 </chapter>