Mention Slony as just an example.

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 7514a097ed6f169b162ff1ebdfb6e5143feef68b..c8e263526e6dd9a2e8c1b6e95028ff7f159c6973 100644 (file)
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Backup and Restore
@@ -1738,13 +1738,14 @@ pg_dumpall -p 5432 | psql -d postgres -p 6543
   
 
   
-   It is also possible to use Slony to create a slave
-   server with the updated version of 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
-   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 Slony to
+   create a slave server with the updated version of
+   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 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.