Lines Matching full:transactions

62  * Below are states for covering allocation transactions.
64  * log write such that no allocation transactions will be re-done during
69  * space allocation transactions which can undo non-transactional changes
71  * already allocated do not result in any transactions. Allocations
79  * The fix for this is to do two dummy transactions when the
86  * These dummy transactions get committed when everything
92  *		we are done covering previous transactions.
98  *		on disk log with no other transactions.
227  * next set of transactions to be aggregated into a checkpoint.
254  * we can avoid the problem of having to hold out new transactions during a
294  * in transactions of varying size. IOWs, it is more consistent to track and
318  * risk running out of free log space to start any new transactions.
343  * new threshold at which we block committing transactions until the background
347  * work. This prevents a process running lots of transactions from overfilling