typos.
--- doc/src/sgml/high-availability.sgml.orig 2011-04-05 08:47:30.000000000 +0200
+++ doc/src/sgml/high-availability.sgml 2011-04-05 08:56:09.000000000 +0200
@@ -486,7 +486,7 @@
<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,8 +944,8 @@
</para>
<para>
- 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
+ After a commit record has been written to disk on the primary, the
+ WAL record is 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.
If the standby is the first matching standby, as specified in
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
