Berkeley DB: txn_commit
Google

ee,hash,hashing,transaction,transactions,locking,logging,access method,access me thods,java,C,C++">

txn_commit


#include <db.h>

int txn_commit(DB_TXN *tid);

Description

The txn_commit function ends the transaction specified by the tid argument.

If DB_TXN_NOSYNC was not specified, a commit log record is written and flushed to disk, as are all previously written log records.

In the case of nested transactions, if the transaction is a parent transaction with unresolved (neither committed or aborted) child transactions, the child transactions are aborted and the commit of the parent will succeed.

In the case of nested transactions, if the transaction is a child transaction, its locks are not released, but are acquired by its parent. While the commit of the child transaction will succeed, the actual resolution of the child transaction is postponed until the parent transaction is committed or aborted, i.e., if its parent transaction commits, it will be committed, and if its parent transaction aborts, it will be aborted.

Any applications that require strict two-phase locking must not release any locks explicitly, leaving them all to be released by txn_commit.

The txn_commit function returns the value of errno on failure, and 0 on success.

Errors

If a fatal error occurs in Berkeley DB, the txn_commit function may fail and return DB_RUNRECOVERY, at which point all subsequent database calls will also return DB_RUNRECOVERY.

The txn_commit function may fail and return errno for any of the errors specified for the following Berkeley DB and C library functions: abort(3), fcntl(3), fflush(3), fprintf(3), free(3), getpid(3), lock_vec, log_put, malloc(3), memcpy(3), memset(3), strerror(3), vfprintf(3), and vsnprintf(3).

In addition, the txn_commit function may fail and return errno for the following conditions:

EINVAL
The transaction was already aborted.

See Also

txn_abort, txn_begin, txn_checkpoint, txn_close, txn_commit, txn_id, txn_open, txn_prepare, txn_stat and txn_unlink.