Berkeley DB: DB_ENV->set_alloc
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_alloc |

`

###

    #include <db.h>

    int
    DB_ENV->set_alloc(DB_ENV *db,
    	void *(*app_malloc)(size_t size),
    	void *(*app_realloc)(void *, size_t),
    	void (*app_free)(void *));

# Description

Set the allocation functions used by the DB_ENV and DB methods to allocate or free memory owned by the application. The DB_ENV->set_alloc interface sets the allocation functions for a database environment; the DB->set_alloc interface sets the allocation functions for a single database. If both are specified, functions specified for a database will be used in preference to functions specified for environment.

There are a number of interfaces in Berkeley DB where memory is allocated by the library and then given to the application. For example, the DB_DBT_MALLOC flag, when specified in the DBT object, will cause the DB methods to allocate and reallocate memory which then becomes the responsibility of the calling application. (See DBT for more information.) Other examples are the Berkeley DB interfaces which return statistical information to the application: DB->stat, lock_stat, log_archive, log_stat, memp_stat, and txn_stat. There is one interface in the Berkeley DB where memory is allocated by the application and then given to the library: DB->associate.

On systems in which there may be multiple library versions of the standard allocation routines (notably Windows NT), transferring memory between the library and the application will fail because the Berkeley DB library allocates memory from a different heap than the application uses to free it. To avoid this problem, the DB_ENV->set_alloc and DB->set_alloc functions can be used to pass Berkeley DB references to the application's allocation routines.

It is not an error to not specify all three arguments to these interfaces; however, in that case the specified interfaces must be compatible with the standard library interfaces, as they will be used together. The functions specified must match the calling conventions of the ANSI C X3.159-1989 (ANSI C) library routines of the same name.

The DB_ENV->set_alloc interface may be used only to configure Berkeley DB before the DB_ENV->open interface is called.

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

# Errors

The DB_ENV->set_alloc 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_alloc 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_alloc 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