From: Bruce Momjian Date: Tue, 16 Oct 2007 19:44:18 +0000 (+0000) Subject: Mention Slony as just an example. X-Git-Url: http://waps.l3s.uni-hannover.de/gitweb/?a=commitdiff_plain;h=afca7b94b1d90fa134c6db240b02820fd3a31c86;p=users%2Fbernd%2Fpostgres.git Mention Slony as just an example. --- diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 77fb2eac77..c1ff4d33cc 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -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.