|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.77 2010/07/03 20:43:57 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.78 2010/07/14 22:04:21 tgl Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="high-availability"> |
4 | 4 | <title>High Availability, Load Balancing, and Replication</title> |
@@ -589,7 +589,7 @@ protocol to make nodes agree on a serializable transactional order. |
589 | 589 | <para> |
590 | 590 | In standby mode, the server continuously applies WAL received from the |
591 | 591 | master server. The standby server can read WAL from a WAL archive |
592 | | - (see <varname>restore_command</>) or directly from the master |
| 592 | + (see <xref linkend="restore-command">) or directly from the master |
593 | 593 | over a TCP connection (streaming replication). The standby server will |
594 | 594 | also attempt to restore any WAL found in the standby cluster's |
595 | 595 | <filename>pg_xlog</> directory. That typically happens after a server |
|