On July 26, 2004 08:43 am, David Parker wrote:
> Say I have 2 geographically separated data centers, East and West, where
> is West is the "warm" backup for East. In East I have 2 databases, A and
> B, where B is a "hot" backup for A, so A is the "master" in that
> replication cluster.
>
> I'm wondering about the best way to set up replication for my database
> C, in the West data center. It is the second level back for A, but I
> would like to avoid adding the load on A of having C making requests
> against it to get updates.
>
> My thought was that I could set up B as the master for C, so when B
> replicated from A, it would trigger a further replication to C, but C
> would only need to connect to B. So the replication chain would be:
> A->B->C.

This is an exact feature of Slony I.
>
> Would this work, or does C need a connection to A for some reason?
Node B subscribes to node A, and Node C subscribes to Node B, Node A does not 
need to know Node C exists.



>
> -  DAP
> ======================================================
> David Parker    Tazz Networks    (401) 709-5130
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general

-- 
Darcy Buskermolen
Wavefire Technologies Corp.
ph: 250.717.0200
fx:  250.763.1759
http://www.wavefire.com