Lines Matching full:transaction

36 In the RDBMS literature, a reservation ticket is associated with a transaction.
39 If the transaction holding the lock is younger, the locking transaction waits.
40 If the transaction holding the lock is older, the locking transaction backs off
43 If the transaction holding the lock is younger, the locking transaction
44 wounds the transaction holding the lock, requesting it to die.
45 If the transaction holding the lock is older, it waits for the other
46 transaction. Hence Wound-Wait.
47 The two algorithms are both fair in that a transaction will eventually succeed.
53 running transaction. Note that this is not the same as process preemption. A
54 Wound-Wait transaction is considered preempted when it dies (returning
68 transaction.
79   killed its transaction after having dropped all already acquired locks.
351   The wounded status of the transaction is checked only when there is
353   situation, if the transaction is wounded, it backs off, clears the
355   this way is that the wounded transaction can identify a contending lock to
356   wait for before restarting the transaction. Just blindly restarting the
357   transaction would likely make the transaction end up in a situation where