BDR is (at the moment) a modified (via patches) PostgreSQL allowing out of the house asynchronous multi-master replication, which seems to perform better than burcado/slony. Although it will be included in PostgreSQL in future releases, it would be great to see it in Gentoo. Would it be possible to add a USE flag that enables the BDR patches? Reproducible: Always
I thought about using the BDR patch with epatch_user, but although they are always talking about a patch they just provide links to their repository with already patched postgresql 9.4 sources. Is there an easy way to change SRC_URI without duplicating the ebuild? Then we could find out whether the ebuild still works properly with the BDR patched sources. Current BDR status: 9.4 needs to be patched (patched version for 9.4.5 available [1]) 9.5 did not merge all of the BDR features yet (no BDR patch available) 9.6 supposed to contain unpatched BDR support (release ~10.2016) [1] http://git.postgresql.org/gitweb/?p=2ndquadrant_bdr.git;a=shortlog;h=refs/heads/bdr-pg/REL9_4_STABLE
Tarballs of the patched postgresql sources and the BDR plugin: http://packages.2ndquadrant.com/postgresql-bdr94-2ndquadrant/tarballs/
(In reply to Benjamin Beier from comment #1) > I thought about using the BDR patch with epatch_user, but although they are > always talking about a patch they just provide links to their repository > with already patched postgresql 9.4 sources. > > Is there an easy way to change SRC_URI without duplicating the ebuild? Then > we could find out whether the ebuild still works properly with the BDR > patched sources. > > Current BDR status: > 9.4 needs to be patched (patched version for 9.4.5 available [1]) > 9.5 did not merge all of the BDR features yet (no BDR patch available) > 9.6 supposed to contain unpatched BDR support (release ~10.2016) > > [1] > http://git.postgresql.org/gitweb/?p=2ndquadrant_bdr.git;a=shortlog;h=refs/ > heads/bdr-pg/REL9_4_STABLE Yes, it's possible to add a bdr USE flag to the SRC_URI like so: !bdr? ( ...unpatched... ) bdr? ( ...patched... ) After having watched a presentation on this, my interest is piqued and I'll probably start working on it sometime in the next couple months as I'm still working on introducing a new eclass. If someone else would like to take a whack at this to get it introduced sooner, it'd be welcomed. Just let me know if any of you start working on it. (Email, IRC, this bug, carrier pigeon....)
There are news: 2ndQuadrant will update their sources to 9.6. They also plan to include BDR in Postgresql 10 upstream. Source: http://blog.2ndquadrant.com/bdr-is-coming-to-postgresql-9-6/
To clarify: There will be no need to run a patched postgresql any more. The extension will work with unmodified postgresql 9.6, as soon as 2ndQuadrant will release BDR for 9.6, making it easier (I guess) to deploy BDR. Kind of as a plugin.
As PostgreSQL 10 is about to come out in September 2018, including the logical replication, further patching won't be necessary anymore. http://rhaas.blogspot.de/2017/04/new-features-coming-in-postgresql-10.html A conclusion of this is, that with PostgreSQL 10 this bug cease to have an further importance, hence it should be marked as such.
(In reply to bgo from comment #6) > As PostgreSQL 10 is about to come out in September 2018, including the > logical replication, further patching won't be necessary anymore. > > http://rhaas.blogspot.de/2017/04/new-features-coming-in-postgresql-10.html > > > A conclusion of this is, that with PostgreSQL 10 this bug cease to have an > further importance, hence it should be marked as such. Thanks for following up on this!
