From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
---|---|
To: | alys brett <alysbrett(at)googlemail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Replication to less secure slave server |
Date: | 2011-01-25 16:25:37 |
Message-ID: | 586AFF34-2850-434B-84CC-3BE0ADA75E70@elevated-dev.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Jan 25, 2011, at 7:04 AM, alys brett wrote:
> I am planning a system that will be hosted within a secure network with very limited access. All access to the database will be from within this network. I need to have a copy of the database available on a much less secure server, which will allow access for web applications. This copy of the database is considered sacrificial.
>
> The replication methods I have read about are focussed on creating standby servers to take over if the primary becomes unavailable. For this, there is obviously a requirement that the slave be able to connect to the database on the master. This is not allowed by our security set-up (that's the whole reason for having the replica database).
>
> I need to somehow push the changes from the master out to the slave. The database is not very complex or large (two main tables with < 100,000 rows) and new rows will be added only every few minutes. A minute or so lag on the copy database is acceptable.
I have similar requirements, so I have the master initiate an SSH reverse tunnel to the replica, where pg connects to the local port that is the remote end of that tunnel.
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
(303) 722-0567 voice
From | Date | Subject | |
---|---|---|---|
Next Message | Ammar Fallaha | 2011-01-26 12:34:27 | Postgres on Windows |
Previous Message | alys brett | 2011-01-25 14:04:26 | Replication to less secure slave server |