Message-ID: <4F7A04FE.8000708@d2.com>
Date: Mon, 02 Apr 2012 12:58:54 -0700
From: amador alvarez <aalvarez@d2.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US;
	rv:1.9.2.27) Gecko/20120216 Lightning/1.0b2 Thunderbird/3.1.19
MIME-Version: 1.0
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
CC: pgsql-admin@postgresql.org
Subject: Re: custom conflict resolution information request
References: <201203291122317598487@gmail.com>
	<4F742D48020000250004692A@gw.wicourts.gov>
	<4F74F9E3.5020807@d2.com>
	<4F79B0560200002500046AB2@gw.wicourts.gov>
In-Reply-To: <4F79B0560200002500046AB2@gw.wicourts.gov>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


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