Re: BDR: name conflict when joining a rebuilt node

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: BDR: name conflict when joining a rebuilt node
Date: 2015-10-30 05:17:35
Message-ID: CAMsr+YHO6ErMSLfimVp_dQeZWHrg_oJ3FBANJ26qCvjQ6o_5_Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 30 October 2015 at 08:24, Florin Andrei <florin(at)andrei(dot)myip(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message rajan 2015-10-30 05:56:32 Unable to select a table as postgres user
Previous Message Dane Foster 2015-10-30 02:39:51 Re: mysql_fdw trouble