Changes since Release 1.5.3.
For additional details, please see the documentation and Release Notes included in your download package or on our website.
Alternatively, the user could commit transactions in "noSync" mode which does not write or flush log buffers and therefore has better performance, but carries a greater risk of losing the transaction if the JVM crashes.
JE 1.7.0 has a new "commitWriteNoSync()" mode which does write but does not flush log buffers at commit time. The transaction will be durable if the JVM crashes, but will not be durable if the OS crashes. CommitWriteNoSync is faster than a synchronous commit and slower than a asynchronous commit. Synchronous, writeNoSync, and noSync modes can be specified through EnvironmentMutableConfig, TransactionConfig, or through Transaction commit(), commitWriteNoSync(), commitNoSync(). [#11131]
Previous versions of JE had a bug where the results of a Database.truncate() call could be seen by other methods run from the same Database handle before the transaction committed, even from other transactions. Environment.truncateDatabase() was introduced to fix the bug without incurring a performance penalty on general operations. [#10339]
Remove output of database=<name> parameter since we do not allow multiple db dumps. [#10861]