darren@up.hrcoxmail.com wrote:
>
> > It is asynchronous without the need of 2 phase commit. It is group
> > communication based and requires the group communication system to
> > guarantee total order. The tricky part is, that the local transaction
> > must be on hold until the own commit message comes back without a prior
>
> No, It holds until it's own Writeset comes back. Commits
> and then send a commit message on the simple channel, so
> commits don't wait for ordered writesets.
>
> Remember total order guarantees if no changes in front of
> the local changes conflict, the local changes can commit.
Right, it's the writeset ... that get's sent just before you flip bits
in the clog, then wait until it comes back and flip 'em.
> >
> > The last time i was playing with spread (that was at Great Bridge in
> > Norfolk), it was IMHO useless (for Postgres-R) because it sometimes
> > dropped messages when the network load got too high. This occured
> > without any indication, no error, nothing. This is not exactly what I
> > understand as total order. I hope they have made some substantial
> > progress on that.
> >
>
> I remember the TCL tester you set up, and having problems,
> but I don't recall investigating what the problems were.
> If you still have the code I can try and reproduce the
> problem, and investigate it on the spread list.
Maybe you heard about it, there was this funny conversation while
walking down the hallway:
"Did that German guy ever turn in his notebook?"
"You mean THIS German guy?"
"Yes, did he turn it in?"
"He is here. Right BEHIND YOU!!!"
"Hummmpf ... er ..."
The stuff was on that notebook. Sorry.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #