Berkeley DB: DB_ENV->set_verbose
Description: Berkeley DB: An embedded database programmatic toolkit.
Keywords: embedded,database,programmatic,toolkit,b+tree,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,java,C,C++

# DB_ENV->set_verbose |

`

###

    #include <db.h>

    int
    DB_ENV->set_verbose(DB_ENV *dbenv, u_int32_t which, int onoff);

# Description

The DB_ENV->set_verbose function turns additional informational and debugging messages in the Berkeley DB message output on and off. If onoff is set to non-zero, the additional messages are output.

The which parameter must be set to one of the following values:

DB_VERB_CHKPOINT
  Display checkpoint location information when searching the log for checkpoints.

DB_VERB_DEADLOCK
  Display additional information when doing deadlock detection.

DB_VERB_RECOVERY
  Display additional information when performing recovery.

DB_VERB_WAITSFOR
  Display the waits-for table when doing deadlock detection.

The DB_ENV->set_verbose interface may be used to configure Berkeley DB at any time during the life of the application.

The DB_ENV->set_verbose function returns a non-zero error value on failure and 0 on success.

The database environment's verbosity 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_verbose", one or more whitespace characters, and the interface which argument as a string; for example, "set_verbose DB_VERB_CHKPOINT". Because the DB_CONFIG file is read when the database environment is opened, it will silently overrule configuration done before that time.

# Errors

The DB_ENV->set_verbose function may fail and return a non-zero error for the following conditions:

EINVAL
  An invalid flag value or parameter was specified.

The DB_ENV->set_verbose function 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_verbose function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.

# See Also

db_env_create, DB_ENV->close, DB_ENV->err, DB_ENV->errx DB_ENV->open, DB_ENV->remove, DB_ENV->set_alloc, DB_ENV->set_cachesize, DB_ENV->set_data_dir, DB_ENV->set_errcall, DB_ENV->set_errfile, DB_ENV->set_errpfx, DB_ENV->set_feedback, DB_ENV->set_flags, DB_ENV->set_mutexlocks, db_env_set_pageyield, DB_ENV->set_paniccall, db_env_set_panicstate, DB_ENV->set_recovery_init, DB_ENV->set_rpc_server, db_env_set_region_init, DB_ENV->set_shm_key, db_env_set_tas_spins, DB_ENV->set_tmp_dir, DB_ENV->set_verbose, db_strerror and db_version.`

Copyright Sleepycat Software