Something worth noting... the only places I've actually seen MM
replication implemented, each master was in fact still responsible
for it's own set of data. It was essentially something that you could
really do with Slony, if you could tolerate the extreme complexity
that would be involved. It might well be worth focusing on that case
first, before trying to come up with a perfect last-committed mechanism.
On Feb 5, 2007, at 5:20 AM, Zeugswetter Andreas ADI SD wrote:
I think you are completely ignoring practicability. Or are you saying,
that such a system exists and works for e.g. a loosly connected
group of
laptop field agents that only sporadically have a connection to the
cluster.
I think Jan's definition gives a pragmatic solution to the problem,
and will be able to give "good" automatic conflict resolution.
It has downsides he stated, and cannot guarantee 100% correct
automatic
conflict
resolution in case of connection loss, but I am quite sure you are not
able to do
better, without loosing yourself in theory.
e.g. assume all clocks vary by no more than 30 seconds when
disconnected, you can
require manual (or rule based) resolution to all conflicts that
vary by
less than
1 minute.
--
Jim Nasby [EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
