|Reported by:||Fernando de Oliveira||Owned by:||Fernando de Oliveira|
Database or Log File On-Disk Format Changes The log file format changed in 184.108.40.206. New Features/Improvements Demonstrated in a sample app how to use thread-specific structures to associate a DB_EVENT_REP_PERM_FAILED event with the transaction that caused it. [#17686] Replication Manager Preferred Master is a new option for 2-site replication groups. One site is the preferred master, which assumes the master role as much of the time as its availability permits. A preferred master replication group guarantees that transactions committed on the preferred master site will never be rolled back while also providing client failover. [#20230] A new flag DB_FORCESYNCENV is provided for DB_ENV->close(), which forces flushing the memory mapped regions before unmapping them. [#21176] A new API is provided to limit the Replication Manager incoming queue based on the amount of heap memory it uses. [#21481] BLOB support is now available for environments configured for replication. [#22359] A new version of DB_ENV->failchk() helps supports multi-process environments which use DB_REGISTER rather than a monitoring process. It is turned on with --enable-failchk_broadcast. [#22419] Added support for Visual Studio 2012. [#22477] CPU time needed for database backups is now reduced. [#22967] Added BDB utilities for the Android platform. [#23079] Added --enable-error_history support. This diagnostic tool prints a stack trace when a panic occurs. [#23119] The new log configuration option DB_LOG_NOSYNC has been added to avoid flushing the transaction log in order to stabilize storage. This can be useful when durability across system crashes is unnecessary and all the transactions in the environment specify either the DB_TXN_NOSYNC or DB_TXN_WRITE_NOSYNC flag. This configuration setting may be made by DB_ENV->log_set_config() or a DB_CONFIG line "db_log_nosync [on|off]". [#23191] Database Environment Changes ... API Changes ... ... Known Bugs ...
Change History (2)
Note: See TracTickets for help on using tickets.