From 900c9962f70b5f276a19d1830a6d3b35cc7215af Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Mon, 20 Nov 2006 15:07:13 +0000
Subject: [PATCH] Update documentation to use Statement-Based Replication
rather than Query Broadcast.
---
doc/src/sgml/high-availability.sgml | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 56733e38e84..69d5ebc84d2 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.1 2006/11/17 16:38:44 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.2 2006/11/20 15:07:13 momjian Exp $ -->
<chapter id="high-availability">
<title>High Availability and Load Balancing</title>
@@ -140,14 +140,14 @@
</varlistentry>
<varlistentry>
- <term>Query Broadcasting</term>
+ <term>Statement-Based Replication</term>
<listitem>
<para>
- In query broadcasting, a program intercepts every SQL query
- and sends it to all servers. Each server operates independently.
- Read-only queries can be sent to a single server because there
- is no need for all servers to process it.
+ In statement-based replication, a program intercepts every SQL
+ query and sends it to all servers. Each server operates
+ independently. Read-only queries can be sent to a single server
+ because there is no need for all servers to process it.
</para>
<para>
--
GitLab