Lines Matching refs:LSN

217 The position in the log is typically referred to as a Log Sequence Number (LSN).
220 offset into the log.  A LSN carries the cycle in the upper 32 bits and the
222 bytes). Hence we can do realtively simple LSN based math to keep track of
249 head contains an LSN and it tracks the physical space usage in the log. While
315 of transactions, their contents and the log sequence number (LSN) of the
318 	Transaction		Contents	LSN
332 forward.  This can be seen in the table above by the changing (increasing) LSN
543 and as such are stored in the Active Item List (AIL) which is a LSN-ordered
713 To do this, transactions need to record the LSN of the commit record of the
714 transaction. This LSN comes directly from the log buffer the transaction is
728 Then, instead of assigning a log buffer LSN to the transaction commit LSN
732 result, the code that forces the log to a specific LSN now needs to ensure that
739 the checkpoint context records the LSN of the commit record for the checkpoint,
763 force the log at the LSN of that transaction) and so the higher level code
966 sequencing needs to wait until checkpoint contexts contain a commit LSN
996 		Write commit LSN into transaction
1006 			Write commit LSN into log item
1063 			Write commit LSN into log item