2
2
3
3
The pglogical module provides logical streaming replication for PostgreSQL,
4
4
using a publish/subscribe module. It is based on technology developed as part
5
- of the BDR project.
5
+ of the BDR project ( http://2ndquadrant.com/BDR ) .
6
6
7
7
We use the following terms to describe data streams between nodes, deliberately
8
8
reused from the earlier Slony technology:
@@ -21,7 +21,7 @@ Use cases supported are:
21
21
* Data gather/merge from multiple upstream servers
22
22
23
23
Architectural details:
24
- * pglogical works on a per-database database level, not whole server level like
24
+ * pglogical works on a per-database level, not whole server level like
25
25
physical streaming replication
26
26
* One Provider may feed multiple Subscribers without incurring additional disk
27
27
write overhead
@@ -485,15 +485,16 @@ It omits some features found in BDR:
485
485
where all nodes' queues are plugged by prevening new xacts from being
486
486
committed, then flushed to the peer nodes. This ensures there are no xacts in
487
487
the queue that can't be applied once table structure has changed. pglogical
488
- doesn't do this, so care must be taken when using mutual multi-master.
488
+ doesn't do this so multi-master replication (where nodes replicate to each
489
+ other) is not yet supported.
489
490
See "limitations".
490
491
491
492
See "limitations and restrictions" for more information.
492
493
493
494
It also adds some features:
494
495
495
496
* Flexible connections between nodes; topology is not restricted to
496
- mesh multi-master . Cascading logical replication is possible.
497
+ a mesh configuration like BDR's . Cascading logical replication is possible.
497
498
498
499
* Loosely-coupled output plugin that's re-usable for other projects
499
500
0 commit comments