In response to Shahaf Abileah <shahaf at redfin.com>:

> Actually, in my case Slony does work well in LAN but does not work at
> all over WAN.  As I understand it, at least one of the slon processes
> (perhaps both) need to communicate with both the master and the slave
> DB.  If the slon process runs in the same location as the master, then
> it needs to communicate with the slave over WAN.  If it runs in the same
> location as the slave then it needs to communicate with the master over
> WAN.  One way or another you'll have a slon process talking across the
> WAN to some DB.  And in our case that simply didn't work.  There was
> enough flakiness in the network between the slon process and the DB that
> replication never got going.

It _does_ work, but the tolerance for network flakiness is only so high.
If your network is constantly dropping, you probably won't be able to
get it going, and you'll have to fall back on something like log
shipping.

-- 
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran at collaborativefusion.com
Phone: 412-422-3463x4023