Berkeley DB

Recovery and Filesystem Operations

When running in a transaction-protected environment, database creation and deletion are logged as standalone transactions internal to Berkeley DB. That is, for each such operation, a new transaction is begun and aborted or committed internally, so that they will be recovered during recovery.

The Berkeley DB API supports removing and renaming files. Renaming files is supported by the DB→rename method, and removing files is supported by the DB→remove method. Berkeley DB does not permit specifying the DB_TRUNCATE flag when opening a file in a transaction-protected environment. This is an implicit file deletion, but one that does not always require the same operating system file permissions as deleting and creating ...