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

Mention Slony as just an example.

Browse Source
This commit is contained in:
Bruce Momjian 2007-10-16 19:44:18 +00:00
parent d8c5edae3b
commit cb0d539d05
1 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.106 2007/10/16 14:56:51 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.107 2007/10/16 19:44:18 momjian Exp $ -->
<chapter id="backup"> <chapter id="backup">
<title>Backup and Restore</title> <title>Backup and Restore</title>
@ -1738,13 +1738,14 @@ pg_dumpall -p 5432 | psql -d postgres -p 6543
</para> </para>
<para> <para>
It is also possible to use <productname>Slony</> to create a slave It is also possible to use replication like <productname>Slony</> to
server with the updated version of <productname>PostgreSQL</>. The create a slave server with the updated version of
slave can be on the same computer or a different computer. Once it <productname>PostgreSQL</>. The slave can be on the same computer or
has synced up with the master server (running the older version of a different computer. Once it has synced up with the master server
<productname>PostgreSQL</>), you can switch masters and make the slave (running the older version of <productname>PostgreSQL</>), you can
the master and shut down the older database instance. Such a switch masters and make the slave the master and shut down the older
switch-over results in only several seconds of downtime for an upgrade. database instance. Such a switch-over results in only several seconds
of downtime for an upgrade.
</para> </para>
<para> <para>