From cb0d539d053866e67a1e719e1af21de130e221e3 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 16 Oct 2007 19:44:18 +0000
Subject: [PATCH] Mention Slony as just an example.

---
 doc/src/sgml/backup.sgml | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 7514a097ed..c8e263526e 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.106 2007/10/16 14:56:51 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.107 2007/10/16 19:44:18 momjian Exp $ -->
 
 <chapter id="backup">
  <title>Backup and Restore</title>
@@ -1738,13 +1738,14 @@ pg_dumpall -p 5432 | psql -d postgres -p 6543
   </para>
 
   <para>
-   It is also possible to use <productname>Slony</> to create a slave
-   server with the updated version of <productname>PostgreSQL</>.  The
-   slave can be on the same computer or a different computer.  Once it
-   has synced up with the master server (running the older version of
-   <productname>PostgreSQL</>), you can switch masters and make the slave
-   the master and shut down the older database instance.  Such a
-   switch-over results in only several seconds of downtime for an upgrade.
+   It is also possible to use replication like <productname>Slony</> to
+   create a slave server with the updated version of
+   <productname>PostgreSQL</>.  The slave can be on the same computer or
+   a different computer.  Once it has synced up with the master server
+   (running the older version of <productname>PostgreSQL</>), you can
+   switch masters and make the slave the master and shut down the older
+   database instance.  Such a switch-over results in only several seconds
+   of downtime for an upgrade.
   </para>
 
   <para>