In an attempt to throw the authorities off his trail, neilc@samurai.com (Neil Conway) transmitted:
> William Yu wrote:
>> Here's my question about "multi-master" replication whether it's
>> Oracle or not. How in the world does it work over high latency, low
>> bandwidth connections w/o getting pummelled in performance?
>
> Well, it may well be the case that it doesn't work :) Not all kinds of
> replication are appropriate for all situations, and I agree that
> synchronous, multi-master replication isn't likely to be useful in the
> situation you describe.
>
> One solution to multi-master replication on slow networks (or networks
> with nodes that are only intermittently connected) is to be very
> asynchronous: transaction commit only affects the local node, and
> conflict resolution is done when replicating changes later. This is
> more useful for filesystem replication: it is easier to do
> after-the-fact conflict resolution, although it is still very
> complex. ISTM it should be possible with DBMS replication, at least in
> theory.
PeerDirect is marketing something that sounds like that...
<http://www.peerdirect.com/products/data_replication_engine/index.ssp>
This sort of "after the fact data synchronization with conflict
resolution" bears marked similarities to:
a) The way PalmOS systems address syncing between a handheld computer
and potentially multiple desktop machines.
It's often most convenient to cut'n'paste changes to things into
one's "Palm Desktop" software because you have higher-bandwidth
input devices like keyboards and mice as compared to scribbling
with a stylus.
I can make changes to data at home or at the office, and when I
HotSync to my PDA, the data starts flowing towards those places it
hasn't been yet...
b) The way Lotus Notes(tm) allowed you to set up queues of messages.
You could update/add material offline, and then "sync up" which
would push/pull changes.
Slony-I and Slony-II won't be doing that, which means that there's
room for someone with interest to have a further usefully-distinct
form of replication.
--
let name="cbbrowne" and tld="gmail.com" in name ^ "@" ^ tld;;
http://linuxdatabases.info/info/slony.html
"At least you know where you are with Microsoft."
"True. I just wish I'd brought a paddle."
