From: | "(Daniel Stolf)" <dstolf(at)gmail(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | adding a bdr node using bcv backup |
Date: | 2016-01-21 00:29:34 |
Message-ID: | CABfnVgUj24yWfA9ztDbkCJpYNpejLfL6uq830+KdjBn=9vnkdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello there...
I'm new to postgres and I'm trying out BDR replication...
I know that when I issue the bdr.bdr_group_join command, it will copy the
entire database from the host I specify on parameter 'join_using_dsn' and
this may take a while depending on the network and the size of the
database...
What I wanted to know is if I can leverage a bcv backup... Is it possible?
I have a 2 nodes on my test environment and wanted to add a 3rd using this
approach... But when I restored the backup, the bdr information from node1
went along, so when I use 'bdr.bdr_group_join', it tells me:
ERROR: This node is already a member of a BDR group
HINT: Connect to the node you wish to add and run bdr_group_join from it
instead
From | Date | Subject | |
---|---|---|---|
Next Message | Melvin Davidson | 2016-01-21 00:44:14 | Re: How to stop autovacuum for daily partition old tables |
Previous Message | AI Rumman | 2016-01-20 23:22:44 | How to stop autovacuum for daily partition old tables |