From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 16 Oct 2007 02:48:57 +0000 (+0000)
Subject: Add mention of Slony for in-place upgrades.
X-Git-Url: http://waps.l3s.uni-hannover.de/gitweb/?a=commitdiff_plain;h=ed4f7e2e517c9407cac240287394bd893d19b288;p=users%2Fbernd%2Fpostgres.git

Add mention of Slony for in-place upgrades.
---

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 8809996616..e675c31524 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1740,6 +1740,16 @@ pg_dumpall -p 5432 | psql -d postgres -p 6543
    access.
   </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 minutes of downtime for an upgrade.
+  </para>
+
   <para>
    In practice you probably want to test your client
    applications on the new setup before switching over completely.