aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2011-02-01 15:21:22 -0500
committerBruce Momjian <bruce@momjian.us>2011-02-01 15:21:22 -0500
commite8cdc238cfa3fda4185fe6a9826dbdf0a107f789 (patch)
treee2f1badf1dd9baf21fe7ea3c77239e10f9db9183 /doc/src
parent902aae5ec58f71b8d9f7efb5ed474d0f5439439d (diff)
downloadpostgresql-e8cdc238cfa3fda4185fe6a9826dbdf0a107f789.tar.gz
postgresql-e8cdc238cfa3fda4185fe6a9826dbdf0a107f789.zip
Document that Slony can do upgrades easier _because_ it supports
replication between different Postgres major versions.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/runtime.sgml2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 4f59fd19c2b..226d616a768 100644
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1704,6 +1704,8 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
<para>
It is also possible to use certain replication methods, such as
<productname>Slony</>, to create a standby server with the updated version of
+ <productname>PostgreSQL</>. This is possible because Slony supports
+ replication between different major versions of
<productname>PostgreSQL</>. The standby 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