diff options
author | Peter Eisentraut <peter_e@gmx.net> | 2012-08-24 22:35:53 -0400 |
---|---|---|
committer | Peter Eisentraut <peter_e@gmx.net> | 2012-08-24 22:35:53 -0400 |
commit | 2e435eb38a9a01894bff6eb2c627083133d729ee (patch) | |
tree | 0f60f91e959b3165779af3868338b611fc38de4d | |
parent | c3ca786df656d447ca02d51ed3a888468ed6e88d (diff) | |
download | postgresql-2e435eb38a9a01894bff6eb2c627083133d729ee.tar.gz postgresql-2e435eb38a9a01894bff6eb2c627083133d729ee.zip |
Normalize some British spellings
-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 f3816085b6f..62f72b40ae0 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -881,7 +881,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass' The cascading replication feature allows a standby server to accept replication connections and stream WAL records to other standbys, acting as a relay. This can be used to reduce the number of direct connections to the master - and also to minimise inter-site bandwidth overheads. + and also to minimize inter-site bandwidth overheads. </para> <para> @@ -1041,7 +1041,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass' <para> Synchronous replication usually requires carefully planned and placed standby servers to ensure applications perform acceptably. Waiting - doesn't utilise system resources, but transaction locks continue to be + doesn't utilize system resources, but transaction locks continue to be held until the transfer is confirmed. As a result, incautious use of synchronous replication will reduce performance for database applications because of increased response times and higher contention. |