Skip to content

Commit de59715

Browse files
committed
Update Statement-Based Replication Middleware docs to be more general.
1 parent dd92a8c commit de59715

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

doc/src/sgml/high-availability.sgml

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.5 2006/11/21 18:15:45 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.6 2006/11/21 18:31:57 momjian Exp $ -->
22

33
<chapter id="high-availability">
44
<title>High Availability and Load Balancing</title>
@@ -166,16 +166,16 @@ protocol to make nodes agree on a serializable transactional order.
166166
</para>
167167

168168
<para>
169-
One limitation of this solution is that functions like
169+
If queries are simply broadcast unmodified, functions like
170170
<function>random()</>, <function>CURRENT_TIMESTAMP</>, and
171-
sequences can have different values on different servers. This
172-
is because each server operates independently, and because SQL
173-
queries are broadcast (and not actual modified rows). If this
174-
is unacceptable, applications must query such values from a
175-
single server and then use those values in write queries.
176-
Also, care must be taken that all transactions either commit
177-
or abort on all servers, perhaps using two-phase commit (<xref
178-
linkend="sql-prepare-transaction"
171+
sequences would have different values on different servers.
172+
This is because each server operates independently, and because
173+
SQL queries are broadcast (and not actual modified rows). If
174+
this is unacceptable, either the middleware or the application
175+
must query such values from a single server and then use those
176+
values in write queries. Also, care must be taken that all
177+
transactions either commit or abort on all servers, perhaps
178+
using two-phase commit (<xref linkend="sql-prepare-transaction"
179179
endterm="sql-prepare-transaction-title"> and <xref
180180
linkend="sql-commit-prepared" endterm="sql-commit-prepared-title">.
181181
Pgpool is an example of this type of replication.

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy