Re: BDR, wal segment has been removed, is it possible move forward?

From: milist ujang <ujang(dot)milist(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: BDR, wal segment has been removed, is it possible move forward?
Date: 2017-09-07 13:16:03
Message-ID: CACG9ogzKCKm1XLpMQtq4MXD=k8xdrYx7MgGypW8VKXMZJ4ivLA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Craig,

On Wed, Sep 6, 2017 at 4:07 PM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:

>
> You could drop and re-create the replication slot, I guess. But your nodes
> would be hopelessly out of sync and need manual resync (with data
> replication disabled) of one node vs another.
>

Thanks for pointing to replication slot.
I Simulate the similar situation in dev env by remove the wal segment on
node1, when node2 keep inserting into a table, now it perfectly can move
forward to latest wal segment, but the difference situation is at
node_status.

In production node_status is i in node1 but r in node2, where on my dev
both nodes keep r , even I waited to let it may change quite long.

can I safely update the node_status directy on bdr.bdr_nodes?

--
regards

ujang jaenudin | DBA Consultant (Freelancer)
http://ora62.wordpress.com
http://id.linkedin.com/pub/ujang-jaenudin/12/64/bab

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message hamann.w 2017-09-07 13:17:49 Re: column names query
Previous Message stimits 2017-09-07 12:58:35 Re: column names query