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


 

Ps : sorry for mistake mail

 

Best regards, 

Sébastien Marchand

Société SGO

 

 

 

 

Cordialement, 

Sébastien Marchand

Société SGO

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20150107/002fd85c/attachment.htm