Skip site navigation (1) Skip section navigation (2)

Re: Database Synchronization

From: Richard Huxton <dev(at)archonet(dot)com>
To: Chris Browne <cbbrowne(at)acm(dot)org>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Database Synchronization
Date: 2007-07-18 15:43:17
Message-ID: 469E3515.4070006@archonet.com (view raw or flat)
Thread:
Lists: pgsql-sql
Chris Browne wrote:
> dev(at)archonet(dot)com (Richard Huxton) writes:
>>
>> http://www.slony.info/

> 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...

Except in the case when you can have separate tables for the data. If 
you have a london_sales table only updated in London and a paris_sales 
table only updated in Paris then you have something inching towards 
multi-master.

-- 
   Richard Huxton
   Archonet Ltd

In response to

Responses

pgsql-sql by date

Next:From: PostgreSQL AdminDate: 2007-07-18 16:46:03
Subject: pgmemcache
Previous:From: Chris BrowneDate: 2007-07-18 14:57:40
Subject: Re: Database Synchronization

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group