Future(s) of PostgreSQL (Multi-Master) Replication
Formal Metadata
| Title | Future(s) of PostgreSQL (Multi-Master) Replication |
|
| Alternative Title | |
| Title of Series | |
| Number of Parts | 29 |
| Author | |
| Contributors | |
| License | CC Attribution - ShareAlike 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Ottawa, Canada |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | BiDirectional Replication
In the course of the BDR (BiDirectional Replication) project we have worked on delivering robust, feature-full and fast asynchronous multi-master replication for postgres. In addition we have started the UDR project, sharing most of the code and infrastructure with BDR, which provides unidirectional logical replication for the many cases where multi-master replication is not required.
To implement BDR a lot of features have already been integrated into core PostgreSQL (9.4). Now that 9.4 is released and BDR/UDR is in production in several complex environment there's some important discussions to be had about what can and what cannot be integrated into core PostgreSQL.
We will discuss:
Which features are in core postgres
Which features does BDR/UDR provide on top of that
What can be integrated into core PostgreSQL and how
Future features
Problems found during the development |
|
