From e61d2521520626cb7744163c02c79e9d2230a3bc Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 16 Oct 2007 02:48:57 +0000
Subject: [PATCH] Add mention of Slony for in-place upgrades.
---
doc/src/sgml/backup.sgml | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 5e8549a2c03..f8ca2b5c481 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.103 2007/09/29 01:36:10 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.104 2007/10/16 02:48:57 momjian Exp $ -->
<chapter id="backup">
<title>Backup and Restore</title>
@@ -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.
--
GitLab