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, which will allow you to add the new database(even empty) to the cluster.
Regards,
Alvaro Aguayo
Jefe de Operaciones
Open Comb Systems E.I.R.L.
Oficina: (+51-1) 3377813 | RPM: #034252 / (+51) 995540103 | RPC: (+51) 954183248
Website: www.ocs.pe
Sent from my Sony Xperia™ smartphone
---- Jonathan Eastgate wrote ----
Hi everyone.
![]()
Keep up to date with simPRO at: http://simprogroup.com/blog
The contents of this email are subject to our email disclaimer.
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 config per database.
Is there any way to configure BDR on a cluster wide basis so that all DB's on a cluster are replicated via BDR instead of having to configure a connection for each DB we want to replicate?
The problem we have is over 20 clusters with about 200 DB's per cluster and growing constantly so this would make deploying BDR a painful process - if we had to add a connection for each existing DB and then every new DB.
Is there a way around this or are there plans to make this type of config available?
Thanks in advance.
Jonathan J. Eastgate
Chief Technology Officer | simPRO Software Group
Ph: 1300 139 467 +61 7 3147 8777
Ph: 1300 139 467 +61 7 3147 8777
Keep up to date with simPRO at: http://simprogroup.com/blog
The contents of this email are subject to our email disclaimer.
--
