Re: PgCon: who will be there?
От | Markus Wanner |
---|---|
Тема | Re: PgCon: who will be there? |
Дата | |
Msg-id | d1ec19a16a79dee738e0c88ac9f86584@localhost обсуждение исходный текст |
Ответ на | Re: PgCon: who will be there? (Greg Sabino Mullane <greg@endpoint.com>) |
Список | pgsql-cluster-hackers |
Hi, On Wed, 3 Mar 2010 10:08:01 -0500, Greg Sabino Mullane <greg@endpoint.com> wrote: > Well, it's all open source for the looking. :) Here's a quick summary. > Basically, Bucardo supports two types of conflict resolution: standard > and custom. The standard includes a handful of default rules about which > side (let's call them A and B) should "win" in a conflict. Options > include 'source' (A), 'target' (B), 'latest' (who made the most recent > change), and 'random' (call it a really weird form of load balancing :). > The custom handlers are much more interesting, as it can incroporate > business logic. Basically, you write a perl subroutine that gets fed > information about the current conflict and returns a code indicating > which side should win. The passed in information also includes handles > to both sides, so that you can query other tables, and even update > the rows in conflict directly. I don't know if any of that is really > applicable to something like Postgres-R, but maybe that's one of the > things we can talk about. Thank you for this quick summary (it's vastly more efficient than having to study source code ;-) ). For Postgres-R, I'm having something akin to your custom handlers in mind. Maybe we can even come up with a compatible interface? I'll certainly have a look at bucardo's custom (conflict resolution) handler interface. Regards Markus Wanner
В списке pgsql-cluster-hackers по дате отправления: