On 07/30/13 10:18, Nicolas Frossard wrote: > Hello dear Slony-1 users, > > I have a simple "one master one slave" scenario but an annoying > requirement: the master and the slave should be able to be configured at > different time, without the other node being necessarily reachable... > > For example, the following should be possible: > > 1- start the master DB (slave DB is not started yet) > 2- init cluster/create set (only on the master) > 3- start slon process on the master > 4- add subscription of slave to the set (only on the master) > > ... some time later ... > > 5- start the slave DB > 6- init cluster/create set (only on the slave) > 7- start slon process on the slave > 9- add subscription of slave to the set (only on the slave) > > ... now the replication is working ! > > unfortunately, it seems that it is impossible to correctly > initialize/configure one node (the master) and then later the other (the > slave). I have to do it at the same time, and both nodes need to be > reachable. > > Is there way to solve this ? I'm using PostgreSQL 9.2 and Slony-1 2.1.3.
The one thing that is impossible in your above description is the STORE NODE command for the second node (slave). For that one, both nodes must be reachable because slonik needs to connect to both databases at the same time. Then again, if the nodes can never reach each other, how are they going to replicate at all? Something in your problem doesn't make sense. Jan -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
