From: Andrew Sullivan <ajs@commandprompt.com>
To: pgsql-general@postgresql.org
Subject: Re: replication
Date: Wed, 25 Jun 2008 08:24:49 -0400
Message-ID: <20080625122448.GB34573@commandprompt.com> (raw)
In-Reply-To: <48623160.4060302@sanbi.ac.za>
References: <4860970E.9070305@careerjunction.co.za>
<ecd779860806242320i35e3f333ue148c62b691da608@mail.gmail.com>
<48623160.4060302@sanbi.ac.za>
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@commandprompt.com
+1 503 667 4564 x104
http://www.commandprompt.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: ajs@commandprompt.com
Subject: Re: replication
In-Reply-To: <20080625122448.GB34573@commandprompt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox