Hi everyone.
We've been testing BDR on and off for the last 2 years and are keen to
start looking at implementing it in production as it seems 0.93 has
resolved most of the issues we faced with it in the early days.
However there is still one item that makes it a difficult proposition...
DSN con
Hello. BDR works on a per-database basis, so there's nothing like what you are
looking for. However, if you initialize a BDR custer with bdr_init_copy, you
will get all existing databases added to replication. Then, as part of the
creation of new databases, you can use bdr_group_join function, w
On 20 July 2016 at 13:22, Jonathan Eastgate
wrote:
> Hi everyone.
>
> We've been testing BDR on and off for the last 2 years and are keen to
> start looking at implementing it in production as it seems 0.93 has
> resolved most of the issues we faced with it in the early days.
>
> However there is
Thanks guys.
Very helpful - I was thinking we may need to look at moving to schemas
instead of individual db's.
I assume that once BDR is enabled on a database that any additional schemas
added post config are automatically included in BDR replication?
And so you see any issues having potentiall
El 20/07/16 a las 20:06, Jonathan Eastgate escribió:
>
> I assume that once BDR is enabled on a database that any additional
> schemas added post config are automatically included in BDR replication?
All DDLs (CREATE SCHEMA ...) will be replicated to the other nodes, but
if you are asking if the