diff options
| author | Robert Haas | 2011-04-05 16:40:17 +0000 |
|---|---|---|
| committer | Robert Haas | 2011-04-05 16:40:17 +0000 |
| commit | ad275473a5ea75f4aa010791884004f75f3c7a65 (patch) | |
| tree | b53b7e43840fb137e13421b4b7a614797876e578 | |
| parent | f5e524d92be609c709825be8995bf77f10880c3b (diff) | |
Typo fixes.
Erik Rijkers
| -rw-r--r-- | doc/src/sgml/high-availability.sgml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 6dbc6bcd721..5972a45555f 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -486,7 +486,7 @@ protocol to make nodes agree on a serializable transactional order. <para> Directly moving WAL records from one database server to another is typically described as log shipping. <productname>PostgreSQL</> - implements file-based log shipping by transfering WAL records + implements file-based log shipping by transferring WAL records one file (WAL segment) at a time. WAL files (16MB) can be shipped easily and cheaply over any distance, whether it be to an adjacent system, another system at the same site, or another system on @@ -944,7 +944,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass' </para> <para> - After a commit record has been written to disk on the primary the + After a commit record has been written to disk on the primary, the WAL record is then sent to the standby. The standby sends reply messages each time a new batch of WAL data is written to disk, unless <varname>wal_receiver_status_interval</> is set to zero on the standby. |