On 6/27/2006 12:47 PM, Alan Hodgson wrote:
> On Tuesday 27 June 2006 09:09, Dan Fitzpatrick <dan at eparklabs.com> wrote:
>> Can Slony handle the following setup:
>>
>>
>> Internal |   DMZ   | External
>> Network  |         | Network
>> ---------|---------|---------
>>  Master  -> Bridge -> Slave
>>    DB         DB       DB
>>
>>
>> In this case, Bridge DB is a slony slave which is the "master" of the
>> external Slave DB.
>>
>> I have a large DB (master) and I want to replicate 2 - 3 tables to an
>> outside server. However, I do not want the master exposed to the outside
>> directly.
>>
>> If this setup does not work with Slony, do you know how else to do this?
> 
> That would work.  
> 
> However, you can also just run the slon process serving the external DB on 
> an internal server.  ie. the external server requires no access back to the 
> internal server.

All that's been said so far is fine. The problem remains that if the 
external server is compromised, it is still possible to affect the 
internal one with events.

If that is a concern, then you want the bridge slave to write log 
shipping files and apply them to the external system(s).


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #