Re: BDR: Can a node live alone after being detached

From: Sylvain MARECHAL <marechal(dot)sylvain2(at)gmail(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: BDR: Can a node live alone after being detached
Date: 2015-06-26 06:56:30
Message-ID: 558CF79E.7040803@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Le 26/06/2015 03:26, Craig Ringer a écrit :
> [...]
>> Sorry to bother again about that, but what about the "detached node cleanup"
>> best practice?
>>
>> Suppose I have 2 nodes, 'node1' and 'node2'. So I am OK to call
>> bdr_part_by_node_names('node2') on node1 to detach node2. But then, is it
>> safe to call bdr_part_by_node_names('node1') to do the cleanup on node2, or
>> should I better call pg_drop_replication_slot('...') instead?
> BDR 0.9.1 drops the slot on remaining nodes correctly on node part, so
> no further action is required there. Just part_by_node_names the node
> you are removing, running the query from one of the nodes you wish to
> retain. (0.9.1 enforces this).
>
> If you want to retain the node you're removing as a standalone, it
> should be sufficient to drop any slots on that node, truncate
> bdr.bdr_nodes and bdr.bdr_connections, and remove the bdr security
> label with:
>
> SECURITY LABEL FOR bdr ON DATABASE thedb IS NULL;
>
> then restart the DB. You may also wish to remove 'bdr' from
> 'shared_preload_libraries'.
>
Thanks a lot,
Sylvain

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tim Smith 2015-06-26 13:38:42 Functions, savepoints, autocommit = I am confused !
Previous Message litu16 2015-06-26 03:23:03 Re: Get the difference between two timestamp cells but in a special format in PostgreSQL