Wed Nov 3 16:42:20 PST 2004
- Previous message: [Slony1-general] problem upgrading to 1.0.5
- Next message: [Slony1-general] One cluster for all replications... or not?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
What is the best perspective concerning several replications running on shared machines? Let's consider I have - for the same project - 2 PostgreSQL servers (on 2 distinct machines): I want the server 1 to be the master for database A and the slave for database B, and the server 2 to be the master for database B and the slave for database A. What does follow the "slony way" the most between : - defining two clusters (one for each database to replicate) with 2 nodes each, - defining a unique clusters with 4 nodes (and making the correct subscriptions)? I first would have separated in different clusters the groups of nodes which have no interactions, but maybe letting slony knows of all the replication of the project can or could be useful/simpler? J?r?mie. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://gborg.postgresql.org/pipermail/slony1-general/attachments/20041103/9d945b3e/attachment.html
- Previous message: [Slony1-general] problem upgrading to 1.0.5
- Next message: [Slony1-general] One cluster for all replications... or not?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list