| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Zhu, Joshua" <jzhu(at)vormetric(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: BDR node removal and rejoin |
| Date: | 2017-07-12 08:58:30 |
| Message-ID: | CAMsr+YF=-UbC1SGPt494ujaZ+MAsQQKQCB4Ji_51bLvB=Gyqsw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11 July 2017 at 05:49, Zhu, Joshua <jzhu(at)vormetric(dot)com> 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 impression that there is no need to perform manual cleanup
> before a removed node (with database dropped and recreated) rejoining a BDR
> group.
>
BDR1 requires that you manually remove the bdr.bdr_nodes entry if you
intend to re-use the same node name.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Albe Laurenz | 2017-07-12 09:31:22 | Re: loading file with en dash character into postgres 9.6.1 database |
| Previous Message | Mark Morgan Lloyd | 2017-07-12 07:20:31 | Systemd support (was:Re: Please say it isn't so) |