pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ian Huynh <ianh@hubspan.com>
To: pgsql-admin@postgresql.org
Subject: Re: Replication
Date: Sun, 31 Aug 2003 20:33:33 -0700
Message-ID: <C499DCDFEDBEBC4BB3B503FF44B41C67035AF9@corpexch01.internal.hubspan.com> (raw)

Thanks for all who replied.
 
There are certain cases where multi-master rep are very implementable such as where
the datasets being rep are fairly disjointed but need to be replicated for completeness in
terms of reporting. But you are absolutely 110% correct. Multimaster synchro is a nightmare.
 
 

	-----Original Message----- 
	From: Christopher Browne [mailto:cbbrowne@acm.org] 
	Sent: Sat 8/30/2003 4:47 PM 
	To: pgsql-admin@postgresql.org 
	Cc: 
	Subject: Re: [ADMIN] Replication
	
	

	Martha Stewart called it a Good Thing whenianh@hubspan.com ("Ian Huynh")wrote:
	> Seems that there are a number of simultaneous project in trying to implement replication
	> for postgres.
	> 
	> Is anyone out there using this feature currently? If so , which package & OS environment.
	> 
	> the latest news was eRServer v1.0.   Is this the same as the v1.2 that Postgres INC announced
	> early this year ?
	> 
	> Is there a master-master capability or only master-multi-slave ?
	
	The version of eRServer recently released as free software is not the
	latest "production" release, but it is a direct predecessor.
	
	Its operational model is that of "master/possible multiple slaves,"
	NOT multimaster.
	
	Multimaster involves some thorny issues surrounding synchronization,
	as it is possible for one master to receive a set of changes
	concurrently with another master receiving _incompatible_ changes.
	
	PalmOS users see this if they change a particular record on both
	desktop and palmtop; the next time they sync, the conflicting record
	normally gets duplicated and the user gets to decide how to fix it.
	
	Doing that in a big production database context may not be
	possible/acceptable.  You only should do multimaster if you REALLY
	know what you're doing.
	--
	select 'aa454' || '@' || 'freenet.carleton.ca';
	http://www.ntlug.org/~cbbrowne/sap.html
	Do you know where your towel is?
	
	---------------------------(end of broadcast)---------------------------
	TIP 4: Don't 'kill -9' the postmaster
	



view thread (63+ messages)  latest in thread

Message-ID: <C499DCDFEDBEBC4BB3B503FF44B41C67035AF9@corpexch01.internal.hubspan.com>
Permalink:  ../C499DCDFEDBEBC4BB3B503FF44B41C67035AF9@corpexch01.internal.hubspan.com/
Also on:    postgresql.org/message-id/C499DCDFEDBEBC4BB3B503FF44B41C67035AF9@corpexch01.internal.hubspan.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: ianh@hubspan.com
  Subject: Re: Replication
  In-Reply-To: <C499DCDFEDBEBC4BB3B503FF44B41C67035AF9@corpexch01.internal.hubspan.com>
  References: <C499DCDFEDBEBC4BB3B503FF44B41C67035AF9@corpexch01.internal.hubspan.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