Date: Wed, 25 Jun 2008 08:24:49 -0400
From: Andrew Sullivan <ajs@commandprompt.com>
To: pgsql-general@postgresql.org
Subject: Re: replication
Message-ID: <20080625122448.GB34573@commandprompt.com>
Mail-Followup-To: Andrew Sullivan <ajs@commandprompt.com>,
	pgsql-general@postgresql.org
References: <4860970E.9070305@careerjunction.co.za>
	<ecd779860806242320i35e3f333ue148c62b691da608@mail.gmail.com>
	<48623160.4060302@sanbi.ac.za>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48623160.4060302@sanbi.ac.za>
User-Agent: Mutt/1.5.17 (2007-11-01)

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/