In response to "Mark Steben" <[EMAIL PROTECTED]>: > > Looking for advice on how to proceed. We are running Postgres 8.2.5 in Lee, > Massachusetts. We will be installing same in Norfolk Virginia in the not > too distant future. Our need is to replicate roughly 60 - 70 percent > Of our 80 GB database in Lee over a WAN to Norfolk for reporting purposes. > In reading 'Slony-1 Best Practices' on the Website I came across the > following statement: > > slon processes should run in the same "network context" as the node that > each is responsible for managing so that the connection to that node is a > "local" one. > Do not run such links across a WAN. > > Does this still hold true? If not I would like to hear experiences of > anyone engaging in a 'Slony-1 long distance relationship' > Any other alternatives to consider? I do run Slony-1.2.14 in development > with everything encompassed in Lee. However > we will be opening another office 35 miles west in West Springfield that I > will be operating out of. I plan on employing Slony-1 > To provide replication between these 2 'not so long distance' locations. > > Any comments welcome. Thanks
I suspect that you're misinterpreting that statement to mean that Slony doesn't work over a WAN. It works very well over a WAN in my experience. That statement is saying that the individual slon daemons should run on the same machine or a machine very close to the machine that they are connecting to as their primary system. I.e. if you're running a slon daemon in Mass, it should not have in it's slon.conf a connection string to the server in Virginia. There should be one slon running in Mass that connects to the Mass DB, and a second one running in Norfolk that connects to the Norfolk DB. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ [EMAIL PROTECTED] Phone: 412-422-3463x4023 _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
