pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedcustom conflict resolution information request
3+ messages / 2 participants
[nested] [flat]
* custom conflict resolution information request
@ 2012-03-30 00:10 amador alvarez <aalvarez@d2.com>
0 siblings, 1 reply; 3+ messages in thread
From: amador alvarez @ 2012-03-30 00:10 UTC (permalink / raw)
To: pgsql-admin
Hi there,
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.
Any clue will be very wellcome,
Thanks in advance,
Amador A.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: custom conflict resolution information request
@ 2012-04-02 18:57 Kevin Grittner <Kevin.Grittner@wicourts.gov>
parent: amador alvarez <aalvarez@d2.com>
0 siblings, 1 reply; 3+ messages in thread
From: Kevin Grittner @ 2012-04-02 18:57 UTC (permalink / raw)
To: amador alvarez <aalvarez@d2.com>; pgsql-admin
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: custom conflict resolution information request
@ 2012-04-02 19:58 amador alvarez <aalvarez@d2.com>
parent: Kevin Grittner <Kevin.Grittner@wicourts.gov>
0 siblings, 0 replies; 3+ messages in thread
From: amador alvarez @ 2012-04-02 19:58 UTC (permalink / raw)
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>; +Cc: pgsql-admin
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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2012-04-02 19:58 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2012-03-30 00:10 custom conflict resolution information request amador alvarez <aalvarez@d2.com>
2012-04-02 18:57 ` Kevin Grittner <Kevin.Grittner@wicourts.gov>
2012-04-02 19:58 ` amador alvarez <aalvarez@d2.com>
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