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
29ad832d
Commit
29ad832d
authored
16 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Document that Bucardo is an example of mulit-master replication with
conflict resolution.
parent
25ca5a9a
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/high-availability.sgml
+2
-1
2 additions, 1 deletion
doc/src/sgml/high-availability.sgml
with
2 additions
and
1 deletion
doc/src/sgml/high-availability.sgml
+
2
−
1
View file @
29ad832d
<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.3
2
2008/
0
1/
30 10:49:55 petere
Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.3
3
2008/
1
1/
17 18:55:14 momjian
Exp $ -->
<chapter id="high-availability">
<chapter id="high-availability">
<title>High Availability, Load Balancing, and Replication</title>
<title>High Availability, Load Balancing, and Replication</title>
...
@@ -212,6 +212,7 @@ protocol to make nodes agree on a serializable transactional order.
...
@@ -212,6 +212,7 @@ protocol to make nodes agree on a serializable transactional order.
server works independently, and periodically communicates with
server works independently, and periodically communicates with
the other servers to identify conflicting transactions. The
the other servers to identify conflicting transactions. The
conflicts can be resolved by users or conflict resolution rules.
conflicts can be resolved by users or conflict resolution rules.
Bucardo is an example of this type of replication.
</para>
</para>
</listitem>
</listitem>
</varlistentry>
</varlistentry>
...
...
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