Shahaf Abileah <shahaf at redfin.com> writes:
>  We are trying to set up a slony slave across two different networks
> over a WAN connection.  Due to network reliability, we want to first
> do the initial subscription for the slave on the same network as the
> master, and then relocate that machine to the other network.  Then,
> we want to tweak the slony paths so that we can use a tunnel through
> a bridgehead server for the synchronization.  :p>
>
> 								       :p> 
>
>   We tried this out with a test database and it seemed to work, data
> was replicating and no errors were reported by slon, but were
> wondering if anyone can think of reasons why this might not work or
> if there is a better way.  In particular, we're not sure if there is
> a better way than manually editing slony paths, and if it is
> acceptable for them to not be consistent between the master and
> slave(s).  Here are the details of what

I would suggest using the slonik "STORE PATH" command to revise the
paths, rather than going into the database and altering the sl_table
directly; that is safer and cleaner.

Aside from that, I'd expect SSH tunnelling to work fine.
-- 
output = reverse("moc.enworbbc" "@" "enworbbc")
http://cbbrowne.com/info/
Would-be National Mottos:
Poland: "We probably would have had a happier history if we were
between Canada and Mexico, not Germany and Russia."