I really couldn't say with the available information.
Can you set provide a step-by-step process by which you set up these nodes?
Le 09/12/2015 05:18, Craig Ringer a écrit :
Are you adding more than one node at once?
BDR isn't currently smart enough to handle that. Make sure to wait
until one node is fully synced up before adding another.
In other words, one shall not attemp to add a new node if the other
nodes are no
Are you adding more than one node at once?
BDR isn't currently smart enough to handle that. Make sure to wait until
one node is fully synced up before adding another.
:* Sylvain Marechal [marechal.sylva...@gmail.com]
*Sent:* Sunday, December 06, 2015 4:23 AM
*To:* Selim Tuvi
*Cc:* pgsql-general@postgresql.org
*Subject:* Re: [GENERAL] bdr manual cleanup required
Did you try this :
https://github.com/2ndQuadrant/bdr/issues/127 :
<
ode to the third node.
-Selim
From: Sylvain Marechal [marechal.sylva...@gmail.com]
Sent: Sunday, December 06, 2015 4:23 AM
To: Selim Tuvi
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] bdr manual cleanup required
Did you try this :
https://github.com/2ndQuadrant/bdr/issu
Did you try this :
https://github.com/2ndQuadrant/bdr/issues/127 :
<<<
BEGIN;
SET LOCAL bdr.skip_ddl_locking = on;
SET LOCAL bdr.permit_unsafe_ddl_commands = on;
SET LOCAL bdr.skip_ddl_replication = on;
SECURITY LABEL FOR bdr ON DATABASE mydb IS NULL;
DELETE FROM bdr.bdr_connections;
DELETE FROM
I am trying to repair a broken bdr cluster setup and so far everything I tried
failed. Under the original node that ran bdr.bdr_group_create I am getting the
following error:
2015-12-04 19:34:29.063 UTC,,,22991,,5661eac4.59cf,1,,2015-12-04 19:34:28
UTC,3/0,0,ERROR,55000,"previous init failed, m
