Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
de597154
Commit
de597154
authored
18 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Update Statement-Based Replication Middleware docs to be more general.
parent
dd92a8c3
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/high-availability.sgml
+10
-10
10 additions, 10 deletions
doc/src/sgml/high-availability.sgml
with
10 additions
and
10 deletions
doc/src/sgml/high-availability.sgml
+
10
−
10
View file @
de597154
<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.
5
2006/11/21 18:
15:45
momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.
6
2006/11/21 18:
31:57
momjian Exp $ -->
<chapter id="high-availability">
<chapter id="high-availability">
<title>High Availability and Load Balancing</title>
<title>High Availability and Load Balancing</title>
...
@@ -166,16 +166,16 @@ protocol to make nodes agree on a serializable transactional order.
...
@@ -166,16 +166,16 @@ protocol to make nodes agree on a serializable transactional order.
</para>
</para>
<para>
<para>
One limitation of this solution is that
functions like
If queries are simply broadcast unmodified,
functions like
<function>random()</>, <function>CURRENT_TIMESTAMP</>, and
<function>random()</>, <function>CURRENT_TIMESTAMP</>, and
sequences
can
have different values on different servers.
This
sequences
would
have different values on different servers.
is because each server operates independently, and because
SQL
This
is because each server operates independently, and because
queries are broadcast (and not actual modified rows). If
this
SQL
queries are broadcast (and not actual modified rows). If
is unacceptable,
applications must query such values from a
this
is unacceptable,
either the middleware or the application
single server and then use those
values in write queries.
must query such values from a
single server and then use those
Also, care must be taken that all
transactions either commit
values in write queries.
Also, care must be taken that all
or abort on all servers, perhaps
using two-phase commit (<xref
transactions either commit
or abort on all servers, perhaps
linkend="sql-prepare-transaction"
using two-phase commit (<xref
linkend="sql-prepare-transaction"
endterm="sql-prepare-transaction-title"> and <xref
endterm="sql-prepare-transaction-title"> and <xref
linkend="sql-commit-prepared" endterm="sql-commit-prepared-title">.
linkend="sql-commit-prepared" endterm="sql-commit-prepared-title">.
Pgpool is an example of this type of replication.
Pgpool is an example of this type of replication.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment