DB_ENV->set_tmp_dir |
#include <db.h>int DB_ENV->set_tmp_dir(DB_ENV *dbenv, const char *dir);
The path of a directory to be used as the location of temporary files. The files created to back in-memory access method databases will be created relative to this path. These temporary files can be quite large, depending on the size of the database.
If no directories are specified, the following alternatives are checked in the specified order. The first existing directory path is used for all temporary files.
Note: environment variables are only checked if one of the DB_USE_ENVIRON or DB_USE_ENVIRON_ROOT flags were specified.
Note: the GetTempPath interface is only checked on Win/32 platforms.
The DB_ENV->set_tmp_dir method configures operations performed using the specified DB_ENV handle, not all operations performed on the underlying database environment.
The DB_ENV->set_tmp_dir 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_tmp_dir must be consistent with the existing environment or corruption can occur.
The DB_ENV->set_tmp_dir method returns a non-zero error value on failure and 0 on success.
The database environment's temporary file directory 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_tmp_dir", one or more whitespace characters, and the directory name. 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_tmp_dir method may fail and return a non-zero error for the following conditions:
Called after DB_ENV->open was called.
The DB_ENV->set_tmp_dir 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_tmp_dir method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.