From: Chris Browne <cbbrowne@acm.org>
Subject: Re: Database Synchronization
Date: Wed, 18 Jul 2007 10:57:40 -0400
Organization: cbbrowne Computing Inc
Lines: 30
Message-ID: <60fy3ln4ij.fsf@dba2.int.libertyrms.com>
References: <002d01c7c90b$48870560$d9951020$@com>
	<469DC124.8000704@archonet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.20 (linux)
Cancel-Lock: sha1:HwUzef0A+QU+pScPo8kG7BziW3U=
To: pgsql-sql@postgresql.org

dev@archonet.com (Richard Huxton) writes:
> Jyoti Seth wrote:
>> Hello ,
>>  I have two postgres databases on different linux servers. Postgres
>> database
>> on one server has some tables that needs to be synchronized from the other
>> postgres database . What should be the best method for this.
>
> The slony replication package lets you choose what tables you
> replicate. On the destination server the tables will be read-only.
>
> http://www.slony.info/
>
> Take a little time to read through the documentation and experiment
> with a test system first. It works fine, but it's got a lot of
> complicated options.

But it is worth noting one thing about the synchronization...

Slony-I's strategy is pretty simple: One node is considered the
"master," and the other node is forcibly made to conform to what is on
the master.

If you want to synchronize back and forth (e.g. - multimaster
replication of some sort), Slony-I is not suitable...
-- 
"cbbrowne","@","linuxdatabases.info"
http://www3.sympatico.ca/cbbrowne/unix.html
Culus thinks  we should go to trade  shows and see how  many people we
can kill by throwing debian cds at them