From ad275473a5ea75f4aa010791884004f75f3c7a65 Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Tue, 5 Apr 2011 12:40:17 -0400 Subject: [PATCH] Typo fixes. Erik Rijkers --- doc/src/sgml/high-availability.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 6dbc6bcd72..5972a45555 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. Directly moving WAL records from one database server to another is typically described as log shipping. 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' - 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 wal_receiver_status_interval is set to zero on the standby.