On 07/01/2015 11:15, Sebastien Marchand wrote: > Hi, > > > > I’m using Slony 2.2.2 with postgresql 9.3. > > Slony work well but i found slony work too on pg, too many access, too many > process,… > > For information slony work in wan with 17 nodes, and 18 replications. > > Replication A > > Server X -> server 1 ( schema base ) > > Server X -> server 2 ( schema base ) > > Server X -> server 3 ( schema base ) > > Server X -> server 4 ( schema base ) > > … > > Server X -> server 17 ( schema base ) > > > > Replication B > > > > Server 1 -> server X ( schema backbase1 ) > > Server 2 -> server X ( schema backbase2 ) > > Server 3 -> server X ( schema backbase3 ) > > Server 4 -> server X ( schema backbase4 ) > > … > > Server 17 -> server X ( schema backbase17 ) > > > > Local.monitor was desactivated to decrease impact on pg. > > I’m using this conf : > > > > /check interval 200/ > > /interval timeout/ 60000 > > group size 50 > > /desired sync time/ 60000 > > cleanup cycles 0 > > log level 0 > > > > i don’t know if someone can help me but i would like to know if my > organisation > with several slon is the good way. > > Better use one replication with 17 set ? perhaps… > >
Hello, If I understand what you wrote, you have a provider for one set of objects in a database that is replicated on 17 different servers. Another set of of objects is then replicated back from every 17 servers to the first one. Could you give more clues on the objects and their organisation in sets ? Are all objects different in all sets ? -- Stéphane Schildknecht Contact régional PostgreSQL pour l'Europe francophone Loxodata - Conseil, expertise et formations
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general
