pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: amador alvarez <aalvarez@d2.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-admin@postgresql.org
Subject: Re: custom conflict resolution information request
Date: Mon, 02 Apr 2012 12:58:54 -0700
Message-ID: <4F7A04FE.8000708@d2.com> (raw)
In-Reply-To: <4F79B0560200002500046AB2@gw.wicourts.gov>
References: <201203291122317598487@gmail.com>
	<4F742D48020000250004692A@gw.wicourts.gov>
	<4F74F9E3.5020807@d2.com>
	<4F79B0560200002500046AB2@gw.wicourts.gov>


What are you using for replication?

-Kevin


Hi Kevin,

I set up a master-master asynchronous replication of one database with bucardo 4.4.5 and testing right now 4.99.3.
I know the standard settings when a conflict between same id rows comes up :

source - the rows on the "source" database always "win" (in a conflict, we copy rows from source to target)


target - the rows on the "target" database always win


skip - any conflicted rows are simply not replicated. Not recommended 
for most cases.


random - each database has an equal chance of winning each time


latest - the row that was most recently changed wins


abort - the sync is aborted on a conflict You can also provide custom 
conflict handlers to allow you to use business logic for better conflict 
resolution.


I have not found info or examples about the custom option yet, and still on the search ...

Cheers,

Amador A.



On 04/02/2012 11:57 AM, Kevin Grittner wrote:
> amador alvarez<aalvarez@d2.com>  wrote:
>
>> I am trying to find any kind of information or examples to deal
>> with custom conflict resolution on swap syncs in a master-master
>> replication.
>
> What are you using for replication?
>
> -Kevin



view thread (3+ messages)

Message-ID: <4F7A04FE.8000708@d2.com>
Permalink:  ../4F7A04FE.8000708@d2.com/
Also on:    postgresql.org/message-id/4F7A04FE.8000708@d2.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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: aalvarez@d2.com, Kevin.Grittner@wicourts.gov
  Subject: Re: custom conflict resolution information request
  In-Reply-To: <4F7A04FE.8000708@d2.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