Lines Matching full:need

138 need to ensure application level data integrity is maintained.
167 changes to the log buffers, we need to ensure that the object we are formatting
196 Hence we avoid the need to lock items when we need to flush outstanding
226 The memory buffer and associated vector need to be passed as a single object,
227 but still need to be associated with the parent object so if the object is
234 are in the item, so we'd need a new encapsulation method for regions in the log
240 Hence we need to keep the vector, but by attaching the memory buffer to it and
252 them to be used without limitations, we need to be able to track and accumulate
290 We need to write these items in the order that they exist in the CIL, and they
291 need to be written as an atomic transaction. The need for all the objects to be
298 To fulfill this requirement, we need to write the entire CIL in a single log
315 might need to tune the recovery transaction object hash size.
319 code to write the changes into the log. To do this efficiently, we need to
345 to store the list of log vectors that need to be written into the transaction.
346 Hence log vectors need to be able to be chained together to allow them to be
411 the log vector chaining. If we track by the log vectors, then we only need to
430 To do this, transactions need to record the LSN of the commit record of the
441 increasing sequence number assigned to it without the need for an external
452 To ensure that we can do this, we need to track all the checkpoint contexts
460 It should be noted that the synchronous forces may need to be extended with
467 are also committed to disk before the one we need to wait for. Therefore we
468 need to check that all the prior contexts in the committing list are also
469 complete before waiting on the one we need to complete. We do this
470 synchronisation in the log force code so that we don't need to wait anywhere
475 is, we need to flush the CIL and potentially wait for it to complete. This is a
491 still need to reserve the space in the log for the checkpoint.
525 reservation needs to be made before the checkpoint is started, and we need to
526 be able to reserve the space without sleeping.  For a 8MB checkpoint, we need a
530 permanent reservation on the space, but we still need to make sure we refresh
535 The problem with this is that it can lead to deadlocks as we may need to commit
553 are added to the CIL and avoid the need for reserving and regranting log space
558 log. Hence as part of the reservation growing, we need to also check the size
560 the maximum threshold, we need to push the CIL to the log. This is effectively