int DB_ENV->set_lk_detect(DB_ENV *dbenv, u_int32_t detect);
Set if the deadlock detector is to be run whenever a lock conflict occurs, and specify what lock request(s) should be rejected. As transactions acquire locks on behalf of a single locker ID, rejecting a lock request associated with a transaction normally requires the transaction be aborted. The specified value must be one of the following list:
The DB_ENV->set_lk_detect method configures a database environment, not only operations performed using the specified DB_ENV handle.
The DB_ENV->set_lk_detect interface may not be called after the DB_ENV->open interface is called. If the database environment already exists when DB_ENV->open is called, the information specified to DB_ENV->set_lk_detect must be consistent with the existing environment or an error will be returned.
The DB_ENV->set_lk_detect method returns a non-zero error value on failure and 0 on success.
The database environment's deadlock detector configuration may also be set using the environment's DB_CONFIG file. The syntax of the entry in that file is a single line with the string "set_lk_detect", one or more whitespace characters, and the interface detect argument as a string; for example, "set_lk_detect DB_LOCK_OLDEST". Because the DB_CONFIG file is read when the database environment is opened, it will silently overrule configuration done before that time.
The DB_ENV->set_lk_detect method may fail and return a non-zero error for the following conditions:
Called after DB_ENV->open was called.
The DB_ENV->set_lk_detect method may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the DB_ENV->set_lk_detect method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
Copyright Sleepycat Software