- Berkeley DB Reference Guide:
- Transaction Subsystem
|
|
There is only a single parameter used in configuring transactions; the DB_TXN_NOSYNC flag. Setting the DB_TXN_NOSYNC flag to DB_ENV->set_flags when opening a transaction region changes the behavior of transactions to not synchronously flush the log during transaction commit.
This change will significantly increase application transactional throughput. However, it means that although transactions will continue to exhibit the ACI (atomicity, consistency, and isolation) properties, they will not have D (durability). Database integrity will be maintained, but it is possible that some number of the most recently committed transactions may be undone during recovery instead of being redone.
The application may also change the number of simultaneous outstanding transactions supported by the Berkeley DB environment by calling the DB_ENV->set_tx_max function. When this number is reached, additional calls to txn_begin will fail until some active transactions complete.
|
|
Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @d1 1 a1 1 @ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d1 1 a1 1 d19 1 a19 1 DB_TXN_NOSYNC flag. Setting the DB_TXN_NOSYNC flag to d33 1 a33 1 calls to DB_ENV->txn_begin will fail until some active transactions @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d18 1 a18 7
The application may change the number of simultaneous outstanding transactions supported by the Berkeley DB environment by calling the DB_ENV->set_tx_max method. This will also set the size of the underlying transaction subsystem's region. When the number of outstanding transactions is reached, additional calls to DB_ENV->txn_begin will fail until some active transactions complete.
There is an additional parameter used in configuring transactions; the d21 3 a23 3 behavior of transactions to not write or synchronously flush the log during transaction commit.
This change may significantly increase application transactional d30 5 @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d19 7 a25 1
There is only a single parameter used in configuring transactions; the d28 3 a30 3 behavior of transactions to not synchronously flush the log during transaction commit.
This change will significantly increase application transactional a36 5
The application may also change the number of simultaneous outstanding transactions supported by the Berkeley DB environment by calling the DB_ENV->set_tx_max function. When this number is reached, additional calls to DB_ENV->txn_begin will fail until some active transactions complete. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d18 1 a18 7
The application may change the number of simultaneous outstanding transactions supported by the Berkeley DB environment by calling the DB_ENV->set_tx_max method. This will also set the size of the underlying transaction subsystem's region. When the number of outstanding transactions is reached, additional calls to DB_ENV->txn_begin will fail until some active transactions complete.
There is an additional parameter used in configuring transactions; the d21 3 a23 3 behavior of transactions to not write or synchronously flush the log during transaction commit.
This change may significantly increase application transactional d30 5 @