Index: doc/src/sgml/failover.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/failover.sgml,v
retrieving revision 1.2
diff -c -r1.2 failover.sgml
*** doc/src/sgml/failover.sgml	26 Oct 2006 17:07:03 -0000	1.2
--- doc/src/sgml/failover.sgml	26 Oct 2006 18:26:21 -0000
***************
*** 29,35 ****
    working together.  Because there is no single solution that eliminates
    the impact of the sync problem for all use cases, there are multiple
    solutions.  Each solution addresses this problem in a different way, and
!   minimizes its impact for a specific workload.
   </para>
  
   <para>
--- 29,40 ----
    working together.  Because there is no single solution that eliminates
    the impact of the sync problem for all use cases, there are multiple
    solutions.  Each solution addresses this problem in a different way, and
!   minimizes its impact for a specific workload.  A few of these solutions are
!   provided with PostgreSQL itself, but it would be impractical for the core
!   database to handle every scenario. That is why most solutions are implemented
!   outside the database. PostgreSQL's unique extensibility is what allows this
!   to happen, and 3rd-party solutions should not be thought of as
!   <qoute>second-rate</> simply because they are not bundled with the database.
   </para>
  
   <para>