1 Master and 2 Slaves... (Replication)

From: "Daniel B(dot) Thurman" <dant(at)cdkkt(dot)com>
To: "Pgadmin-Support \(E-mail\)" <pgadmin-support(at)postgresql(dot)org>
Subject: 1 Master and 2 Slaves... (Replication)
Date: 2007-09-22 14:00:31
Message-ID: 021126B987E43D44A860139823C079110E2B7C@orion.cdkkt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support


I started out with a simple master and slave server arrangement and was successfully
able to get the master to replicate to the slave. But once I added a second slave, things
got much more confusing.

I had assumed that adding replication to a second slave server, the relationship would
remain between the second slave and the master and that the second slave would not
know anything of the first slave and vice versa?

I have noticed that adding a second slave, there were additional objects added to
itself, the master, the first slave, and 1 additional subscription set, 1 additional slave nodes!

In other words, the master and the slaves "know" about each other?

This means that for every additional server being added, you have to go back and configure
all of the other servers that "knows" about this new addition?

The odd thing so far, my master/slave replication still works, but I wonder when the shite will
hit the fan...

Is there any documentation that explains this somehwhere?

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.488 / Virus Database: 269.13.28/1021 - Release Date: 9/21/2007 2:02 PM

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Charlie Clark 2007-09-22 14:15:40 Re: Weird characters saved in SQL file
Previous Message Horvath Gabor 2007-09-22 12:06:17 1.8-Beta5 Bug: sequence properties dialog produces wrong sql statement order