Lines Matching refs:sequence

25 That is, if we have a sequence of changes A through to F, and the object was
27 of transactions, their contents and the log sequence number (LSN) of the
334 checkpoint sequence order is maintained during log replay.
416 committed transactions with the log sequence number of the transaction commit.
431 contexts, and as such it is simple to assign a sequence number to each
434 increasing sequence number assigned to it without the need for an external
435 atomic counter - we can just take the current context sequence number and add
439 during the commit, we can assign the current checkpoint sequence. This allows
441 checkpoint sequence needs to be committed before they can continue. As a
467 case where the forcing sequence number is the same as the current context. That
469 simple addition to the existing log forcing code to check the sequence numbers
470 and push if required. Indeed, placing the current sequence checkpoint flush in
749 		Write CIL context sequence into transaction
760 		sequence commit records