On 14 July 2017 at 00:09, Zhu, Joshua wrote:
>
>
> Found these log entries from one of the other node:
>
>
>
> t=2017-07-13 08:35:34 PDT p=27292 a=DEBUG: 0: found valid replication
> identifier 15
>
> t=2017-07-13 08:35:34 PDT p=27292 a=LOCATION:
> bdr_establish_connection_and_slot, bdr.c:60
Ringer [mailto:cr...@2ndquadrant.com]
Sent: Wednesday, July 12, 2017 11:59 PM
To: Zhu, Joshua
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] BDR node removal and rejoin
On 13 July 2017 at 01:56, Zhu, Joshua
mailto:j...@vormetric.com>> wrote:
Thanks for the clarification.
Looks lik
On 13 July 2017 at 01:56, Zhu, Joshua wrote:
> Thanks for the clarification.
>
>
>
> Looks like I am running into a different issue: while trying to pin down
> precisely the steps (and the order in which to perform them) needed to
> remove/rejoin a node, the removal/rejoining exercise was repeate
[mailto:cr...@2ndquadrant.com]
Sent: Wednesday, July 12, 2017 1:59 AM
To: Zhu, Joshua
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] BDR node removal and rejoin
On 11 July 2017 at 05:49, Zhu, Joshua
mailto:j...@vormetric.com>> wrote:
An update… after manually removing the record for
On 11 July 2017 at 05:49, Zhu, Joshua wrote:
> An update… after manually removing the record for ‘node4’ from
> bdr.bdr_nodes, corresponding record in bdr.bdr_connections, and associated
> replication slot (with pg_drop_replication_slot), rejoining was successful.
>
>
>
> I was under the impressi
An update... after manually removing the record for 'node4' from bdr.bdr_nodes,
corresponding record in bdr.bdr_connections, and associated replication slot
(with pg_drop_replication_slot), rejoining was successful.
I was under the impression that there is no need to perform manual cleanup
befo
