From f55e6c07c37aa4e995ee9445e484a52ac77670a9 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 8 Nov 2007 22:14:18 +0000
Subject: [PATCH] Wording improvement for pl/proxy mention.
---
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 05b72441570..78467d57318 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.20 2007/11/08 22:08:18 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.21 2007/11/08 22:14:18 momjian Exp $ -->
<chapter id="high-availability">
<title>High Availability, Load Balancing, and Replication</title>
@@ -193,7 +193,7 @@ protocol to make nodes agree on a serializable transactional order.
endterm="sql-prepare-transaction-title"> and <xref
linkend="sql-commit-prepared" endterm="sql-commit-prepared-title">.
Pgpool and Sequoia are an example of this type of replication.
- This can be implemented using the PL/Proxy toolset as well.
+ Also, this can be implemented using the PL/Proxy toolset.
</para>
</listitem>
</varlistentry>
--
GitLab