Re: [GENERAL] BDR: cascading setup

On 11 January 2016 at 18:55, Oleksii Kliukin wrote: > We are evaluating BDR for a multi-master cross-datacenter replication, > with 2 masters actually communicating across datacenter, supplemented by a > local in-datacenter replicas to provide HA. > This is strongly desirable ... but not curren

Re: [GENERAL] Postgres BDR bdr_init_copy fails

On 15 January 2016 at 03:41, Nikhil wrote: > > pg_ctl: another server might be running; trying to start server anyway > > It looks like you may have run bdr_init_copy on a non-empty data directory containing an existing server. -- Craig Ringer http://www.2ndQuadrant.com/ P

Re: [GENERAL] [BDR] Best practice to automatically abort a DDL operation when one node is down

On 13 January 2016 at 21:45, Sylvain MARECHAL wrote: > The problem is that the (1) DDL request will wait indefinitely, meaning > all transactions will continue to fail until the DDL operation is manually > aborted (for example, doing CTRL C in psql to abort the "CREATE TABLE"). > Correct, and b

Re: [GENERAL] Adding node to bdr group

> Can I just do a bdr.bdr_group_join ? Just want to confirm what the best practice is as I haven't seen anything in the documentation about this. Yes, you can just do a bdr.bdr_group_join ( http://bdr-project.org/