already
exists before trying to create it and move along if it's already there?
Thanks a lot!
On Fri, Jan 22, 2016 at 6:57 AM Craig Ringer wrote:
> On 21 January 2016 at 20:46, (Daniel Stolf) wrote:
>
>
>> So here's what I don't ge
n | restart_lsn
---++---++--++--+--+-
(0 rows)
On Thu, Jan 21, 2016 at 10:46 AM (Daniel Stolf) wrote:
> Ok, I'm at work now and I have access to my lab...
>
> * On Node 1: *
> bdrdemo=# select bdr.bdr_get_local_nodei
#x27;t they need the if of
node3 on their name?
2) If node3 has the same name and if as node1, won't that introduce a
conflic? Don't I need to clean that up before node3 can join the
replication group?
Regards,
Daniel Stolf
On Thu, Jan 21, 2016 at 8:34 AM (Daniel Stolf) wrote:
> Hi Cr
brought up the copy, if I try get local node name, it says
node1, which is the node I got the copy from, ... Wouldn't I also have to
do something about that? Like, delete the previous information on bdr
database that went along?
Em qui, 21 de jan de 2016 00:50, Craig Ringer
escreveu:
> On
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.
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.
