Thursday, May 18, 2006

Conceptual Challenge for Transactions

So, if I can pause and resume a transction, and in between pause and resume, the updates made are permenant. But the question is then, in between pause and resume, how should the tentative transaction behave? Should it still react to invalidation msgs?

Now it is clear to me that the tentative codes are still subject to the invalidation mesgs. It should make sense now that the tentative codes should not expand or shink the suspended transaction's read/write sets but rather only update write set's log if it happens to collide with the write set.

No comments: