mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add mention of Slony for in-place upgrades.

Browse Source
This commit is contained in:
Bruce Momjian 2007-10-16 02:48:57 +00:00
parent febd60bf5d
commit e61d252152
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/src/sgml/backup.sgml
View File

@ -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"> <chapter id="backup">
<title>Backup and Restore</title> <title>Backup and Restore</title>
@ -1740,6 +1740,16 @@ pg_dumpall -p 5432 | psql -d postgres -p 6543
access. access.
</para> </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> <para>
In practice you probably want to test your client In practice you probably want to test your client
applications on the new setup before switching over completely. applications on the new setup before switching over completely.