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