|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.69 2010/05/28 14:03:31 heikki Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.70 2010/05/29 09:01:10 heikki Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="high-availability"> |
4 | 4 | <title>High Availability, Load Balancing, and Replication</title> |
@@ -714,7 +714,7 @@ trigger_file = '/path/to/trigger_file' |
714 | 714 |
|
715 | 715 | <para> |
716 | 716 | If you're using a WAL archive, its size can be minimized using |
717 | | - the <varname>restartpoint_command</> option to remove files that are no |
| 717 | + the <varname>restartpoint_command</> option to remove files that are |
718 | 718 | no longer required by the standby server. Note however, that if you're |
719 | 719 | using the archive for backup purposes, you need to retain files needed |
720 | 720 | to recover from at least the latest base backup, even if they're no |
@@ -1089,7 +1089,7 @@ if (!triggered) |
1089 | 1089 | <para> |
1090 | 1090 | It is also possible to implement record-based log shipping using this |
1091 | 1091 | alternative method, though this requires custom development, and changes |
1092 | | - will still onlybecomes visible to hot standby queries after a full WAL |
| 1092 | + will still onlybecome visible to hot standby queries after a full WAL |
1093 | 1093 | file has been shipped. |
1094 | 1094 | </para> |
1095 | 1095 |
|
|