Lines Matching refs:reservation

53 a special log reservation known as a permanent transaction reservation. A
56 of reservation size limitations. Hence a rolling extent removal transaction
486 The big issue for a checkpoint transaction is the log space reservation for the
494 usage of the transaction. The reservation accounts for log record headers,
510 space.  From this, it should be obvious that a static log space reservation is
514 Further, if we are going to use a static reservation, which bit of the entire
515 reservation does it cover? We account for space used by the transaction
516 reservation by tracking the space currently used by the object in the CIL and
518 relogged. This allows for a checkpoint reservation to only have to account for
521 However, even using a static reservation for just the log metadata is
523 1MB of log space consumed (512 bytes per 32k) and the reservation needs to be
525 reservation needs to be made before the checkpoint is started, and we need to
527 reservation of around 150KB, which is a non-trivial amount of space.
529 A static reservation needs to manipulate the log grant counters - we can take a
530 permanent reservation on the space, but we still need to make sure we refresh
531 the write reservation (the actual space available to the transaction) after
548 available in their reservation for this as they have already reserved the
549 maximal amount of log metadata space they require, and such a delta reservation
550 will always be less than or equal to the maximal amount in the reservation.
552 Hence we can grow the checkpoint transaction reservation dynamically as items
558 log. Hence as part of the reservation growing, we need to also check the size
559 of the reservation against the maximum allowed transaction size. If we reach