Lines Matching refs:written

23 changes in the new transaction that is written to the log.
26 written to disk after change D, we would see in the log the following series
35 	    <object written to disk>
102 buffers. It is clear that reducing the number of stale objects written to the
126 written to the log at any point in time, there may be a much greater amount
147 	1. Reduce the amount of metadata written to the log by at least
248 them so that they can be written to the log at some later point in time.  The
253 The log item is already used to track the log items that have been written to
254 the log but not yet written to disk. Such log items are considered "active"
257 completion, after which they are unpinned and can be written to disk. An object
283 all the items in the CIL must be written into the log via the log buffers.
285 need to be written as an atomic transaction. The need for all the objects to be
286 written as an atomic transaction comes from the requirements of relogging and
331 checkpoints to be written into the log buffers in the case of log force heavy
339 to store the list of log vectors that need to be written into the transaction.
393 Once the checkpoint is written into the log buffers, the checkpoint context is
394 attached to the log buffer that the commit record was written to along with a
425 written into. While this works just fine for the existing transaction
427 written directly into the log buffers. Hence some other method of sequencing