Re: BDR: name conflict when joining a rebuilt node - Mailing list pgsql-general

From Craig Ringer
Subject Re: BDR: name conflict when joining a rebuilt node
Date
Msg-id CAMsr+YHO6ErMSLfimVp_dQeZWHrg_oJ3FBANJ26qCvjQ6o_5_Q@mail.gmail.com
Whole thread Raw
In response to BDR: name conflict when joining a rebuilt node  (Florin Andrei <florin@andrei.myip.org>)
Responses Re: BDR: name conflict when joining a rebuilt node  (Florin Andrei <florin@andrei.myip.org>)
List pgsql-general
On 30 October 2015 at 08:24, Florin Andrei <florin@andrei.myip.org> wrote:

> The problem is, bdr_node_join_wait_for_ready() never returns, it just waits
> forever. If I go on pg11 and run SELECT * FROM bdr.bdr_nodes, I see pg12
> listed twice, with node_status k and i, respectively. On pg11 I see this in
> the logs:
>
> "System identification mismatch between connection and slot","Connection for
> bdr (6211167104388615363,1,16387,) resulted in slot on node bdr
> (6211167104388615363,1,17163,) instead of expected node",,,,,,,,"bdr
> (6211167104388615363,1,17163,): perdb"

This is a bug fixed in 0.9.3.

https://github.com/2ndQuadrant/bdr/issues/126


--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-general by date:

Previous
From: Dane Foster
Date:
Subject: Re: mysql_fdw trouble
Next
From: rajan
Date:
Subject: Unable to select a table as postgres user