Berkeley DB 3.0.55 Change Log

Database On-Disk Format Changes:

The on-disk Btree/Recno format has changed from version 6 to version 7, and the on-disk Hash format has changed from version 5 to version 6. For information on upgrading database formats, see section 3.3, "Upgrading databases" in the Berkeley DB Reference Guide

Major New Features:

A new Access Method has been added to Berkeley DB: the Queue Access Method. The Queue Access Method is similar to the Recno Access Method, but is implemented to provide significantly higher-concurrency queue-oriented append and consume operations.

Database creation and removal are now optionally transaction protected.

Berkeley DB now includes a complete Tcl API.

Berkeley DB now optionally creates dynamic shared libraries.

Interface Changes:

The Berkeley DB interfaces have been reworked in the 3.0.55 release for two reasons. The goals were as follows: to make the Berkeley DB structures opaque so future releases of Berkeley DB can be binary compatible with each other, provide enhanced error checking and reporting during Berkeley DB environment and database configuration and creation, provide configurability throughout the lifetime of the environment and database, and to make the Berkeley DB interfaces consistent across the C++, C and Java APIs.

While the C API changes are extensive, they are also simple to understand. No functionality was removed. The changes required comparatively few modifications to the C++ and Java APIs, mostly limited to moving methods among classes and the addition of a new flag value to a few interfaces. For specific instructions on upgrading Berkeley DB 2.X applications to this release, see the "Upgrading Berkeley DB 2.X.X applications to Berkeley DB 3.0" chapter in the Berkeley DB Reference Guide.

The following individual changes are all part of this larger change.

Function changes:

The db_appinit and db_appexit functions have been replaced by the db_env_create function and the DBENV->open and DBENV->close methods. The db_open function has been removed, replaced by the db_create function and the DB->open method. Berkeley DB environments are now created using the db_env_create function followed by methods on the handle it returns. Berkeley DB databases are now created using the db_create function followed by methods on the handle it returns.

The lock_open, lock_close and lock_unlink functions have been replaced by the db_env_create function and the DBENV->open, DBENV->close and DBENV->remove methods. The remaining lock subsystem functions now take a DBENV handle as their first argument instead of a DB_LOCKTAB handle.

The log_open, log_close and log_unlink functions have been replaced by the db_env_create function and the DBENV->open, DBENV->close and DBENV->remove methods. The remaining log subsystem functions now take a DBENV handle as their first argument instead of a DB_LOG handle.

The memp_open, memp_close and memp_unlink functions have been replaced by the db_env_create function and the DBENV->open, DBENV->close and DBENV->remove methods. The remaining shared memory buffer pool functions now take a DBENV handle as their first argument instead of a DB_MPOOL handle.

The txn_open, txn_close and txn_unlink functions have been replaced by the db_env_create function and the DBENV->open, DBENV->close and DBENV->remove methods. The remaining transaction subsystem functions now take a DBENV handle as their first argument instead of a DB_TXNMGR handle.

The db_jump_set and db_value_set functions have been replaced by methods on the DBENV handle.

The db_xa_open routine has been replaced by a new flag, DB_XA_CREATE, which is passed to the db_create function.

DBENV structure changes:

The db_errcall, db_errfile, db_errpfx and db_paniccall fields of the DBENV structure have been deprecated and their functionality replaced by the DBENV->set_errcall, DBENV->set_errfile, DBENV->set_errpfx and DBENV->set_paniccall methods.

The db_verbose field of the DBENV structure has been replaced by the DBENV->set_verbose method.

The lk_conflicts, lk_detect, lk_max and lk_modes fields of the DBENV structure have been replaced by the DBENV->set_lk_conflicts, DBENV->set_lk_detect and DBENV->set_lk_max methods.

The lg_max field of the DBENV structure has been replaced by the DBENV->set_lg_max method.

The mp_mmapsize and mp_size fields of the DBENV structure have been replaced by the DBENV->set_cachesize and DBENV->set_mp_mmapsize methods.

The tx_info, tx_max and tx_recover fields of the DBENV structure have been replaced by the DBENV->set_tx_max and DBENV->set_tx_recover methods.

The (unused) DBENV->db_lorder field has been deleted.

DB structure changes:

The byteswapped field of the DB structure has been replaced by the DB->get_byteswapped method.

The db_errcall, db_errfile, db_errpfx and db_paniccall fields of the DB structure have been deprecated and their functionality replaced by the DB->set_errcall, DB->set_errfile, DB->set_errpfx and DB->set_paniccall methods.

The type field of the DB structure has been replaced by the DB->get_type method.

DBINFO structure changes:

The bt_compare field of the DB structure has been replaced by the DB->set_bt_compare method.

The bt_minkey field of the DB structure has been replaced by the DB->set_bt_minkey method.

The bt_prefix field of the DB structure has been replaced by the DB->set_bt_prefix method.

The db_cachesize field of the DB structure has been replaced by the DB->set_cachesize method.

The db_lorder field of the DB structure has been replaced by the DB->set_lorder method.

The db_malloc field of the DB structure has been replaced by the DB->set_malloc method.

The db_pagesize field of the DB structure has been replaced by the DB->set_pagesize method.

The dup_compare field of the DB structure has been replaced by the DB->set_dupcompare method.

The flags field of the DB structure has been replaced by the DB->set_flags method.

The h_ffactor field of the DB structure has been replaced by the DB->set_h_ffactor method.

The h_hash field of the DB structure has been replaced by the DB->set_h_hash method.

The h_nelem field of the DB structure has been replaced by the DB->set_h_nelem method.

The re_delim field of the DB structure has been replaced by the DB->set_re_delim method.

The re_len field of the DB structure has been replaced by the DB->set_re_len method.

The re_pad field of the DB structure has been replaced by the DB->set_re_pad method.

The re_source field of the DB structure has been replaced by the DB->set_re_source method.

The use of the POSIX EAGAIN error return to indicate deadlock has been replaced with the Berkeley DB specific error DB_LOCK_DEADLOCK. Note: this change could potentially cause subtle errors. Programs must be updated or the Berkeley DB distribution altered for programs to run correctly. See the "Upgrading Berkeley DB 2.X.X applications to Berkeley DB 3.0" chapter in the Berkeley DB Reference Guide for more information.

The DB_RMW flag to the DB->cursor method has been renamed to be DB_WRITECURSOR (note, this change is applicable only to the Berkeley DB Concurrent Data Store product).

The DB_LOCK structure is no longer a simple integer value. For this reason, the DB_LOCK argument to the lock_put interface has been changed to be a reference to a DB_LOCK structure instead of the DB_LOCK structure itself.

The db_home argument to the environment creation function (historically db_appinit, now DBENV->open) now overrides the DB_HOME environment variable; this is necessary so that the -h option to the various Berkeley DB utilities can override the user's environment.

A mode argument was added to the environment creation function (historically db_appinit, now DBENV->open) to allow applications to specify the mode of files created in the Berkeley DB environment.

The DB_LOCKDOWN flag was added to enable applications to attempt to lock shared memory regions into physical memory.

General Environment Changes:

A new flag has been added to the DBENV->open method, DB_SYSTEM_MEM. This flag causes Berkeley DB to attempt to allocate memory for its shared regions from system shared memory. This flag supports functionality similar to that previously provided by the DB_REGION_ANON and DB_REGION_NAME flags to the db_value_set interface.

A new flag has been added to the DBENV->open method, DB_PRIVATE. This flag causes Berkeley DB to attempt to allocate memory for its shared regions from the heap and to assume that only inter-thread mutexes are required, and not inter-process ones as well. This flag is a superset of the functionality previously provided by the DB_MPOOL_PRIVATE flag to the memp_open interface.

There is a new DBENV method, DBENV->remove, that removes entire Berkeley DB environments.

There are two new methods, DBENV->set_feedback and DB->set_feedback, that allow applications to specify a callback function that is to be called with periodic progress updates on various Berkeley DB operations.

There is a new DBENV method, DBENV->set_recovery_init, that allows applications to install application-specific recovery functions before Berkeley DB performs recovery.

There is a new DBENV method, DBENV->set_verbose, that allows applications to request verbose information from the Berkeley DB library.

The Berkeley DB 3.0.55 release includes enhanced functionality for reporting Berkeley DB returned errors. There are two new DBENV methods, DBENV->err and DBENV->errx, and two new DB methods, DB->err and DB->errx, which allow applications to format and report Berkeley DB error returns using any of the historic output channels. There is an additional function, db_strerror, which is a superset of the ANSI C standard strerror function, providing error strings for both the Berkeley DB errors and underlying system errors.

There is a new DBENV method, DBENV->set_lg_bsize, that allows applications to specify the size of the in-memory log buffer.

Reduce the number of file descriptors used to support fcntl locking from one-per-region to a single one.

Fix a bug where specifying any one-character directory in the db_config argument or other related configuration interface would fail.

Fix a bug where recovery could fail if only a single checkpoint had ever been written.

Fix a bug where threads could race when regions were grown. Because there exist systems where mutexes cannot be unmapped and then remapped back into application memory, the functionality to grow regions has been removed from the Berkeley DB 3.0.55 release. This means that selecting a correct initial region size (e.g., based on the number of active transactions) is more important than before. To facilitate this, region high-water marks have been added to the region statistics where appropriate.

General Access Method Changes:

There is a new DB method, DB->remove, that deletes a database in a transaction-protected operation.

There is a new DB method, DB->upgrade, that upgrades the on-disk format of an underlying database.

There is a new DB method, DB->set_realloc, that allows applications to specify a local memory reallocation function similarly to the previously available DB->set_malloc functionality.

The DB->open method supports a new flag, DB_EXCL, which behaves similarly to the POSIX O_EXCL system open call flag.

The Berkeley DB 3.0.55 release includes enhanced functionality for reporting Berkeley DB returned errors. There are two new DBENV methods, DBENV->err and DBENV->errx, and two new DB methods, DB->err and DB->errx, which allow applications to format and report Berkeley DB error returns using any of the historic output channels. There is an additional function, db_strerror, which is a superset of the ANSI C standard strerror function, providing error strings for both the Berkeley DB errors and underlying system errors.

The last two arguments to the DB->join method were reversed for consistency with the rest of the Berkeley DB interfaces taking cursor references and flags arguments.

A cursor duplication method has been added to the DBcursor handle. This method can be used to duplicate a cursor's transaction and locker ID, and, optionally, to duplicate its position in the database. This change adds useful functionality, and more importantly makes it possible to write applications that both use locking without transactions and have multiple cursors in the same thread of control.

There is a new DBT structure flag, DB_DBT_REALLOC, that allows threaded applications to re-use a single piece of memory for multiple Berkeley DB retrievals, similarly to the DB_DBT_MALLOC flag.

Enhance in-memory databases so that operations on them may be transaction protected. Fix a bug where specifying logging and transactions on an in-memory database could cause a core dump.

Change Berkeley DB recovery to not undo operations performed by logged, but not transaction protected operations.

Change Berkeley DB to no longer generate new locker IDs for every cursor in non-threaded environments to greatly reduce the possibility of self-deadlock.

Change the "dbopen" function in the Berkeley DB 1.85 compatibility API to "__dbopen185" so that we don't collide with the C library where the C library is version 1.85.

Fix multiple bugs where joins did not correctly work in the presence of unsorted duplicates or duplicate duplicates.

Fix an erroneous error message by removing diagnostic code which assumed that closing a cursor closed all locks held by the cursor locker ID.

Fix a bug in the default overflow comparison routine such that if the overflow comparison test failed because we ran out of key bytes, but were also on the last page of the overflow item, we would return equality even though there were remaining bytes in the overflow item.

Fix a bug where read-only databases were registered with the logging subsystem, causing Berkeley DB recovery to open and close them.

Fix a bug where it was (remotely) possible for a file registered with the logging subsystem to be incorrectly evaluated as not logging changes.

Fix a bug where the read-modify-write flag was set in the DB->put method when the database was not configured for locking.

Fix two bugs where the DB->join and DB->put methods assumed that the only possible error was DB_NOTFOUND, thus failing to return deadlock errors to the application.

Fix a bug where illegal flags to the DB->cursor method weren't caught.

Fix a bug where illegal flags to the DBcursor->c_get method weren't caught.

Fix a bug where the DB_NEXT_DUP flag could be specified with an uninitialized cursor.

Fix a bug where the DB->sync and DB->close methods did not return the DB_INCOMPLETE error if it occurred.

Fix a bug where off-page duplicate splits could cause cursors to be mis-positioned.

Fix a bug where partial puts of fixed-length records could cause data corruption.

Fix a set of potential bugs where the OSF/1 and gcc compilers will use instructions requiring alignment on unaligned data.

Fix multiple bugs with large numbers of duplicate records including large numbers of duplicate duplicate records.

Btree Access Method Changes:

The on-disk Btree/Recno format has changed from version 6 to version 7, required due to a change in the database metadata page.

The Btree cursor routines have been rewritten to use the new cursor duplicate functionality. This fixed a couple of bugs where specific sequences of database operations could cause the cursor to become mis-positioned in the database and made it less likely that similar bugs can be introduced in the future.

Applications may now optionally turn off reverse-splitting in Btree databases.

Btree split operations have been reworked to acquire the metadata page lock last, and only if the split is going to succeed. This significantly increases the possible level of concurrency in small databases.

Fix a bug where database corruption could occur if enough threads writing to a small database all schedule page splits.

Fix a bug where the DB_SET_RANGE option could return an already deleted on-page duplicate record to the application.

Fix a bug where an application could core dump if deadlock occurred during cursor close.

Fix a bug where applications with high-concurrency requirements could encounter races.

Fix a bug where read serializability was incorrect.

Fix a bug where records of the wrong endian-ness were not correctly imported.

Fix a bug where an application's cursor could be mis-positioned if a split failed unexpectedly.

Fix a bug where the DB_SET_RECNO, DB_SET and DB_GET_BOTH flags could potentially return inexact matches under some circumstances.

Fix a bug where searches could potentially leave pages in the database locked.

Fix a bug where deleted records could potentially be left in the database after all cursors were closed.

Fix a bug where deleting the last duplicate entry on a page could cause an application core dump.

Fix a bug where a page lock could be incorrectly discarded when moving through on-page duplicate items.

Fix a bug where retrieval of a specific duplicate data item could cause a core dump.

Fix a bug where DB_CURRENT could erroneously release the cursor's page lock.

Fix a bug where the DB->del interface to a Btree database could leave a cursor mis-positioned under some circumstances.

Fix a memory leak when using the DB->del interface to delete records.

Fix a bug where specifying the DB_DBT_PARTIAL flag and a dbt.off value when creating a new record included garbage in the record.

Fix a bug where Btree statistics did not correctly account for overflow and off-page duplicate pages.

Fix a bug where Btree statistics could fail and leave database pages locked.

Fix a bug where page LSNs could be lost during recovery of a page split.

Fix a bug where empty pages in big-endian databases were not always correctly converted.

Fix a bug where previously deleted records could be accessed on the page, leading to potentially incorrect behavior.

Fix a bug where on-page duplicates could be corrupted when reading non-native-endian databases.

Hash Access Method Changes:

The on-disk Hash format has changed from version 5 to version 6, required due to a change in the database metadata page.

In order to allow hash databases as subdatabases, hash will allocate groups of contiguous pages. This may cause some hash databases to appear much larger than they actually are (i.e., they will be sparse files).

Statistics, returned by the DB->stat method, have been added to the Hash Access Method.

Fix a bug where initial access of a duplicate data item could cause future access of other items to fail.

Fix a bug where puts or deletes could cause cursors on the same page to reference incorrect entries.

Fix a bug where partial gets from on-page duplicates could be wrong.

Fix a set of bugs where error paths could lead to application failure.

Fix a set of bugs where cursors could be mis-positioned after operations on off-page duplicates or off-page duplicates could be stored in incorrect sorted order.

Fix a bug where overwriting duplicate items could fail.

Fix a bug where an error return value could be overwritten when releasing the metadata page.

Queue Access Method Changes:

Recno Access Method Changes:

Support read-only backing source files for Recno databases.

Fix a bug where accessing the backing source file name could find incorrect information or cause a core dump.

Fix a bug where the length of fixed-length Recno records were not correctly byte-swapped during database load.

Fix a set of related bugs where the DB_DBT_PARTIAL flag was incorrectly handled when manipulating fixed-length records.

Fix a bug where the key created by the DB_AFTER and DB_BEFORE operations was not correctly returned.

Fix a set of related bugs where certain sequences of operations could leave application cursors mis-positioned.

Fix a bug where deleting the last record in a database could leave an application cursor mis-positioned.

Fix a bug where DB_APPEND returned an error instead of appending to the database.

Fix a bug where specifying the DB_CURRENT, DB_FIRST or DB_NEXT flags could fail because insufficient records had been read from the backing file.

Fix a bug where page splits could result in an incorrect previous page pointer.

Fix a bug where the DB_GET_BOTH flag was permitted for Recno, which does not support it.

C++ API Changes:

Remove the DbLockTab, DbLog, DbMpool and DbTxnMgr classes, moving their methods to the DbEnv class.

Replace the set_error_model method with the DB_CXX_NO_EXCEPTIONS flag to the DbEnv class constructor.

Added constructor with a single flag argument for DbEnv and Db. Added (nonstatic) open methods to DbEnv, Db.

Methods (such as DbLock::put) that used to have a DbMpool, DbLockTab, DbLog, or DbTxnMgr pointer argument, now take a DbEnv pointer argument.

Added DbEnv::set_feedback(), DbEnv::set_recovery_init().

Added DbEnv::strerror(), DbEnv::err(), DbEnv::errx()

Added BtrecExample, a Btree record example.

Fix a bug where the error model was not set before the initial environment was opened.

Java API Changes:

Remove the DbLockTab, DbLog, DbMpool and DbTxnMgr classes, moving their methods to the DbEnv class.

Added constructor with a single flag argument for DbEnv and Db. Added (nonstatic) open methods to DbEnv, Db.

Methods (such as DbLock.put) that used to have a DbMpool, DbLockTab, DbLog or DbTxnMgr argument, now take a DbEnv argument.

Added DbEnvFeedback, DbRecoverInit interfaces that are used as 'callbacks' with DbEnv.set_feedback(), DbEnv.set_recovery_init().

Updated AccessExample to illustrate technique of subclassing from Dbt to handle arbitrary data types, in this case to create a StringDbt class.

Tcl API Changes:

XA Resource Manager Changes:

Fix a bug where it was possible to specify both JOIN and RESUME to the XA start interface.

Fix a bug where the current txn ID was not invalidated after commit/prepare/abort, as the resource manager process does not call xa_end.

Fix a bug where the TMRESUME and TMONEPHASE flags were incorrectly checked in the xa_start interface.

Locking Subsystem Changes:

The lock_detect interface has been modified to optionally return a count of the number of deadlocks broken.

The lock_detect routine has been modified to break as many deadlocks as possible during each run instead of returning after breaking a single deadlock.

The lock subsystem lock_put and lock_vec calls will no longer return DB_LOCK_NOTHELD or EACCES errors under any circumstances to indicate that a lock was held by another locker.

The lock_stat function now returns the following additional information:

st_lock_id: The last allocated lock ID.

st_maxnlockers: The maximum lockers at any one time.

The lock_stat function no longer returns the following information:

st_magic: The magic number that identifies a file as a lock file.

st_numobjs: The number of unique objects locked.

st_refcnt: The number of references to the region.

st_version: The version of the lock file type.

Lock IDs are now allowed to wrap, rather than being limited to two billion.

Fix a bug in lock detection where it was possible to lose track of lockers.

Fix a bug where all locks held on an object were not necessarily released when DB_LOCK_PUT_OBJ was requested.

Fix a bug where the lock subsystem did not detect a lock conflict if there was no transaction.

Fix a bug where lock_detect could treat the DB_LOCK_OLDEST and DB_LOCK_YOUNGEST flags as semantically equivalent.

Fix a bug where locks waiting on an aborted lock were not correctly promoted at the time of the abort.

Fix a bug where committing a child that held no locks was treated as an error.

Fix a bug where deadlock detection was done incorrectly in the case of transactions with nested children.

Fix a bug where parent transactions which had never obtained locks were incorrectly handled when child transactions committed.

Fix a bug where the library could dump core if multiple deadlock detectors were running simultaneously.

Logging Subsystem Changes:

The log_register function no longer takes a DBTYPE argument.

Open log files with the Windows FILE_FLAG_WRITE_THROUGH flag on Windows systems that support it.

Make verbose message "Finding last valid log LSN" optional based on the DBENV->set_verbose method.

Modify log to not attempt to allocate unreasonably large buffers when reading garbage from the log.

Modify log_register to re-use file identifiers to avoid running out in applications that repeatedly open and close files.

The log_stat function now returns the following additional information:

st_lg_bsize: The in-memory log record cache size.

st_wcount: The number of times the log has been written to disk.

st_wcount_fill: The number of times the log has been written to disk because the in-memory log record cache filled up.

The log_stat function no longer returns the following information:

st_refcnt: The number of references to the region.

Fix a bug where the last-known-LSN-on-disk wasn't being set correctly, causing the next log_flush call to decide not to flush the current contents of the buffer to disk, and losing the recovery checkpoint record.

Fix a bug where recovery was not returning the next-to-last checkpoint, rather it always returned the last checkpoint.

Fix a number of related bugs in file registry, that could lead to crashes during recovery in applications that repeatedly created, opened and closed files.

Buffer Pool Subsystem Changes:

The Berkeley DB 3.0.55 release still limits the buffer pool to a 4GB cache. However, the method for setting the Berkeley DB buffer cache size, DBENV->set_cachesize, has been changed to allow applications to specify cache sizes larger than 4GB, in preparation for relaxing that limitation. In addition, applications may specify that multiple pieces of shared memory are to be used to create the cache, for architectures that do not support 4GB chunks of contiguous shared memory.

Add a new semantic for memp_sync, if the LSN argument is NULL, flush the entire buffer cache.

The DB_MPOOL_PRIVATE flag to the db_appinit and memp_open functions has been removed, replaced by the DB_PRIVATE flag to the DBENV->open method.

The memp_stat function no longer returns the following information:

st_refcnt: The number of references to the region.

Allow for OS-specific functions that preallocate pages in files since non-POSIX systems (read as "Windows") will give you garbage in the middle of a file (let's talk about security).

Fix a bug where transaction checkpoint could pin down the entire buffer cache, starving requests for new buffers.

Fix a bug where systems with large POSIX pthread structures could allocate too little memory for the default pool.

Fix a bug where highly concurrent systems could end up with incorrect buffers-to-flush counts during cache syncs.

Fix a bug where the wrong page number could be used when allocating new pages.

Transaction Subsystem Changes:

The txn_begin function now takes a flag parameter. This allows specification of synchronous or asynchronous log flushing behavior on a per-transaction basis during begin. Applications may also specify a flag that causes Berkeley DB to return an error immediately if any lock is unavailable, rather than waiting for the lock.

The txn_commit function now takes a flag parameter. This allows specification of synchronous or asynchronous log flushing behavior on a per-transaction basis during commit.

The txn_stat function now returns the following additional information:

st_maxnactive: The maximum number of active transactions at any one time.

parentid: The st_txnarray structure includes a new field, parentid, which is the the transaction ID of the parent transaction (or 0, if no parent).

The txn_stat function no longer returns the following information:

st_refcnt: The number of references to the region.

Do not complain about "missing files" during recovery if no operations were performed on the file.

Free the recovery dispatch table after recovery has completed.

Fix a bug where it was possible to overwrite the checkpoint LSN during checkpoint.

Fix a bug where an uncommitted child TXN was not committed when its parent TXN committed.

Fix a bug where nested transactions could be undone in an incorrect order in the presence of parents making modifications to pages already modified by the child.

Utility Changes:

Change the output of the db_dump utility to support subdatabases. The db_load utility supports both the old and new input formats of the db_dump utility.

Add the -k option to the db_dump utility to support dumping Queue and Recno databases without altering their key values.

Add the -l and -s options to the db_dump utility to support subdatabases.

Modify the -d option to the db_dump utility to support different output formats as part of recovery testing.

Modify the -N option for utilities supporting it to not only not acquire Berkeley DB mutexes, but to also ignore any other potentially fatal errors or corruption.

Add the -e option to db_stat, to display per-environment statistics.

Add the -s options to the db_stat utility to support subdatabases.

The db_stat utility will now print out page or record numbers when displaying lock information for locks obtained by the access methods.

Fix a bug where db_stat could drop core if called incorrectly.

Fix a bug where db_recover would force regions to be created at the default size instead of the size requested by the application.

Fix bugs where the db_checkpoint and db_deadlock utilities incorrectly wrote their process IDs to their log files.

Fix bugs where some of the Berkeley DB provided utilities had inconsistent POSIX signal handling. Block SIGPIPE on applicable systems in case the utility output is being piped to another process.

Configuration, Documentation, Portability and Build Changes:

The documentation has been extensively rewritten and enhanced, in particular, the Berkeley DB Reference Guide has been completed.

The University of California, Berkeley copyright clause relating to acknowledgement within advertising materials has been deleted from the Berkeley DB copyrights.

Berkeley DB now optionally builds dynamic shared libraries, see the --enable-dynamic configuration option for more information.

Add support on Windows for sharing files in system-specific way supporting the new DB_SYSTEM_MEM.

The Windows/3.1 support has been removed from the distribution.

Java support has been integrated in the project file that is part of the Visual C++ workspace.

Java support has been integrated into the standard build Makefile.

Changed DLL names to use conventions like libdb30d.dll. Debug vs. release libraries and different release numbered libraries can now be distinguished.

The Solaris/Sparc V9 platform has 8-byte dev_t, ino_t and time_t values, which required the database file unique ID to be rewritten.

The configuration include file for Berkeley DB has been renamed from "config.h" to "db_config.h" to minimize the potential for name collision with other packages.

Some C++ operator=() methods that did not have a return type now have return type void.

Allow for different JNI's implementation of AttachCurrentThread().

Multiple changes to make it easier for applications to use the Berkeley DB recovery infrastructure to accomplish recovery of their own objects.

Separate out the Berkeley DB distribution script that creates the log marshalling/unmarshalling layer source code so that it can be called separately by application-specific logging code.

Add a file to the build_unix subdirectory, some Linux releases have archive exploders that will not extract directories containing only symbolic links.

The external variable errno support has been extracted out of the main library source code, and is now encapsulated in a single source file.

Rename the getlong() subroutine to __db_getlong() to eliminate a potential namespace collision.