| From: | Andrew Sullivan <ajs(at)commandprompt(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: replication |
| Date: | 2008-06-25 12:24:49 |
| Message-ID: | 20080625122448.GB34573@commandprompt.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jun 25, 2008 at 01:52:00PM +0200, Allan Kamau wrote:
> Initially you may want to get the full dump (this applies also to the
> replication option) across to your other site.
Most of the replication systems I've seen require that _they_ send the
data to the remote site, so copying the data yourself is actually a
waste of bandwidth, since it's all going to get copied anyway. (They
have to do this because that's how they know that they're starting
from a point in time for which they have consistency information.)
You can indeed save on bandwith, however, by tunnelling your postgres
connections through an ssh tunnel that's using compression.
A
--
Andrew Sullivan
ajs(at)commandprompt(dot)com
+1 503 667 4564 x104
http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2008-06-25 12:26:51 | Re: Reg : Data base deletion |
| Previous Message | Bill Moran | 2008-06-25 12:19:08 | Re: pg_dump estimation |