head 1.2; access; symbols RPM_4_2_1:1.1.1.5 RPM_4_2:1.1.1.5 RPM_4_1_1:1.1.1.5 RPM_4_1:1.1.1.4 RPM_4_0_5:1.1.1.3 RPM_4_0_4:1.1.1.2 RPM_4_0_3:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.52.53; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.36; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.31.26; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.48.56; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.10.15.03.47.30; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.56; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB: DB_ENV->set_flags

DB_ENV->set_flags

 APIRef 

#include <db.h>


int
DB_ENV->set_flags(DB_ENV *dbenv, u_int32_t flags, int onoff);

Description

The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more of the following values: If onoff is set to zero, the specified flags are cleared; otherwise they are set.

DB_CDB_ALLDB
For Berkeley DB Concurrent Data Store applications, perform locking on an environment-wide basis rather than per-database. This flag may be used only to configure Berkeley DB before the DB_ENV->open interface is called.

DB_NOMMAP
Copy read-only database files in this environment into the local cache instead of potentially mapping them into process memory (see the description of the DB_ENV->set_mp_mmapsize function for further information).

DB_TXN_NOSYNC
Do not synchronously flush the log on transaction commit or prepare. This means that transactions exhibit the ACI (atomicity, consistency, and isolation) properties, but not D (durability); that is, database integrity will be maintained, but it is possible that some number of the most recently committed transactions may be undone during recovery.

The number of transactions potentially at risk is governed by how often the log is checkpointed (see db_checkpoint for more information) and how many log updates can fit into the log buffer.

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

The database environment's flag values 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_flags", one or more whitespace characters, and the interface flag argument as a string; for example, "set_flags DB_TXN_NOSYNC". 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_flags 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_flags 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_flags 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.

APIRef

Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @@ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d30 1 a30 1 If onoff is d35 3 a37 9

DB_CDB_ALLDB
If set, Berkeley DB Concurrent Data Store applications will perform locking on an environment-wide basis rather than on a per-database basis. The DB_CDB_ALLDB flag may be used to configure Berkeley DB only before the DB_ENV->open interface is called.

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either make this same call or the DB_CDB_ALLDB flag should be specified in the DB_CONFIG configuration file. d39 3 a41 5

DB_NOLOCKING
If set, Berkeley DB will grant all requested mutual exclusion mutexes and database locks without regard for their actual availability. This functionality should never be used for purposes other than debugging.

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). d43 8 a50 65

DB_NOMMAP
If set, Berkeley DB will copy read-only database files into the local cache instead of potentially mapping them into process memory (see the description of the DB_ENV->set_mp_mmapsize function for further information).

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either make this same call or the DB_NOMMAP flag should be specified in the DB_CONFIG configuration file.

DB_NOPANIC
If set, Berkeley DB will ignore any panic state in the database environment. (Database environments in a panic state normally refuse all attempts to call Berkeley DB functions, returning DB_RUNRECOVERY.) This functionality should never be used for purposes other than debugging.

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle).

DB_PANIC_ENVIRONMENT
If set, Berkeley DB will set the panic state for the database environment. (Database environments in a panic state normally refuse all attempts to call Berkeley DB functions, returning DB_RUNRECOVERY.) This flag may not be specified using the environment's DB_CONFIG file. This flag may be used to configure Berkeley DB only after the DB_ENV->open interface is called.

This call affects all threads of control using the database environment.

DB_REGION_INIT
In some applications, the expense of page-faulting the underlying shared memory regions can affect performance. (For example, if the page-fault occurs while holding a lock, other lock requests can convoy, and overall throughput may decrease.) If set, Berkeley DB will page-fault shared regions into memory when initially creating or joining a Berkeley DB environment. In addition, Berkeley DB will write the shared regions when creating an environment, forcing the underlying virtual memory and filesystems to instantiate both the necessary memory and the necessary disk space. This can also avoid out-of-disk space failures later on.

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

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either make this same call or the DB_REGION_INIT flag should be specified in the DB_CONFIG configuration file.

DB_TXN_NOSYNC
If set, Berkeley DB will not synchronously flush the log on transaction commit or prepare. This means that transactions exhibit the ACI (atomicity, consistency, and isolation) properties, but not D (durability); that is, database integrity will be maintained, but it is possible that some number of the most recently committed transactions may be undone during recovery. The number of transactions potentially at risk is governed by how often the log is checkpointed (see db_checkpoint for more information) and how many log updates can fit into the log buffer.

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either make this same call or the DB_TXN_NOSYNC flag should be specified in the DB_CONFIG configuration file.

DB_YIELDCPU
If set, Berkeley DB will yield the processor immediately after each page or mutex acquisition. This functionality should never be used for purposes other than stress testing.

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either make this same call or the DB_YIELDCPU flag should be specified in the DB_CONFIG configuration file. d83 2 d86 1 d89 1 d91 1 a91 1 DB_ENV->set_tas_spins, a92 1 DB_ENV->set_timeout, @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d2 1 a2 1 a3 1 a33 14

DB_AUTO_COMMIT
If set, operations for which no explicit transaction handle was specified, and which modify databases in the database environment, will be automatically enclosed within a transaction. If the call succeeds, changes made by the operation will be recoverable. If the call fails, the operation will have made no changes.

Calling DB_ENV->set_flags with the DB_AUTO_COMMIT flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_AUTO_COMMIT flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_AUTO_COMMIT flag may be used to configure Berkeley DB at any time during the life of the application. d36 8 a43 10 basis rather than on a per-database basis.

Calling DB_ENV->set_flags with the DB_CDB_ALLDB flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_CDB_ALLDB flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_CDB_ALLDB flag may be used to configure Berkeley DB only before the DB_ENV->open interface is called. a44 24

DB_DIRECT_DB
If set and supported by the system, Berkeley DB will turn off system buffering of Berkeley DB database files to avoid double caching.

Calling DB_ENV->set_flags with the DB_DIRECT_DB flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_DIRECT_DB flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_DIRECT_DB flag may be used to configure Berkeley DB at any time during the life of the application.

DB_DIRECT_LOG
If set and supported by the system, Berkeley DB will turn off system buffering of Berkeley DB log files to avoid double caching.

Calling DB_ENV->set_flags with the DB_DIRECT_LOG flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_DIRECT_LOG flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_DIRECT_LOG flag may be used to configure Berkeley DB at any time during the life of the application. d48 3 a50 6

Calling DB_ENV->set_flags with the DB_NOLOCKING flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle).

The DB_NOLOCKING flag may be used to configure Berkeley DB at any time during the life of the application. d53 1 a53 1 description of the DB_ENV->set_mp_mmapsize method for further d55 6 a60 10

Calling DB_ENV->set_flags with the DB_NOMMAP flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_NOMMAP flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_NOMMAP flag may be used to configure Berkeley DB at any time during the life of the application. d65 3 a67 17

Calling DB_ENV->set_flags with the DB_NOPANIC flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle).

The DB_NOPANIC flag may be used to configure Berkeley DB at any time during the life of the application.

DB_OVERWRITE
Overwrite files stored in encrypted formats before deleting them. Berkeley DB overwrites files using alternating 0xff, 0x00 and 0xff byte patterns. For file overwriting to be effective, the underlying file must be stored on a fixed-block filesystem. Systems with journaling or logging filesystems will require operating system support and probably modification of the Berkeley DB sources.

Calling DB_ENV->set_flags with the DB_OVERWRITE flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle).

The DB_OVERWRITE flag may be used to configure Berkeley DB at any time during the life of the application. d74 3 a76 6

Calling DB_ENV->set_flags with the DB_PANIC_ENVIRONMENT flag affects the database environment, including all threads of control accessing the database environment.

The DB_PANIC_ENVIRONMENT flag may be used to configure Berkeley DB at any time during the life of the application. d86 22 a107 49

Calling DB_ENV->set_flags with the DB_REGION_INIT flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_REGION_INIT flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_REGION_INIT flag may be used to configure Berkeley DB at any time during the life of the application.

DB_TXN_NOSYNC
If set, Berkeley DB will not write or synchronously flush the log on transaction commit or prepare. This means that transactions exhibit the ACI (atomicity, consistency, and isolation) properties, but not D (durability); that is, database integrity will be maintained, but if the application or system fails, it is possible some number of the most recently committed transactions may be undone during recovery. The number of transactions at risk is governed by how many log updates can fit into the log buffer, how often the operating system flushes dirty buffers to disk, and how often the log is checkpointed

Calling DB_ENV->set_flags with the DB_TXN_NOSYNC flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_TXN_NOSYNC flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_TXN_NOSYNC flag may be used to configure Berkeley DB at any time during the life of the application.

DB_TXN_WRITE_NOSYNC
If set, Berkeley DB will write, but will not synchronously flush, the log on transaction commit or prepare. This means that transactions exhibit the ACI (atomicity, consistency, and isolation) properties, but not D (durability); that is, database integrity will be maintained, but if the system fails, it is possible some number of the most recently committed transactions may be undone during recovery. The number of transactions at risk is governed by how often the system flushes dirty buffers to disk and how often the log is checkpointed.

Calling DB_ENV->set_flags with the DB_TXN_WRITE_NOSYNC flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_TXN_WRITE_NOSYNC flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_TXN_WRITE_NOSYNC flag may be used to configure Berkeley DB at any time during the life of the application. d111 5 a115 9

Calling DB_ENV->set_flags with the DB_YIELDCPU flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_YIELDCPU flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_YIELDCPU flag may be used to configure Berkeley DB at any time during the life of the application. d117 1 a117 1

The DB_ENV->set_flags method returns a non-zero error value on failure and 0 on success. d126 1 a126 1

The DB_ENV->set_flags method may fail and return a non-zero error for the following conditions: d130 4 a133 6

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

Class

DB_ENV d135 24 a158 1 Database Environments and Related Methods @ 1.1.1.4 log @Import: RPM 4.1 @ text @d2 1 a2 1 d4 1 d35 14 d51 10 a60 8 basis rather than on a per-database basis. The DB_CDB_ALLDB flag may be used to configure Berkeley DB only before the DB_ENV->open interface is called.

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either make this same call or the DB_CDB_ALLDB flag should be specified in the DB_CONFIG configuration file. d62 24 d89 6 a94 3

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). d97 1 a97 1 description of the DB_ENV->set_mp_mmapsize function for further d99 10 a108 6

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either make this same call or the DB_NOMMAP flag should be specified in the DB_CONFIG configuration file. d113 17 a129 3

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). d136 6 a141 3

This call affects all threads of control using the database environment. d151 49 a199 22

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

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either make this same call or the DB_REGION_INIT flag should be specified in the DB_CONFIG configuration file.

DB_TXN_NOSYNC
If set, Berkeley DB will not synchronously flush the log on transaction commit or prepare. This means that transactions exhibit the ACI (atomicity, consistency, and isolation) properties, but not D (durability); that is, database integrity will be maintained, but it is possible that some number of the most recently committed transactions may be undone during recovery. The number of transactions potentially at risk is governed by how often the log is checkpointed (see db_checkpoint for more information) and how many log updates can fit into the log buffer.

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either make this same call or the DB_TXN_NOSYNC flag should be specified in the DB_CONFIG configuration file. d203 9 a211 5

This call affects only the specified DB_ENV handle (and any handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either make this same call or the DB_YIELDCPU flag should be specified in the DB_CONFIG configuration file. d213 1 a213 1

The DB_ENV->set_flags function returns a non-zero error value on failure and 0 on success. d222 1 a222 1

The DB_ENV->set_flags function may fail and return a non-zero error for the following conditions: d226 6 a231 4

The DB_ENV->set_flags 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_flags function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d233 1 a233 24 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_paniccall, DB_ENV->set_recovery_init, DB_ENV->set_rpc_server, DB_ENV->set_shm_key, DB_ENV->set_tas_spins, DB_ENV->set_tmp_dir, DB_ENV->set_timeout, DB_ENV->set_verbose, db_strerror and db_version. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d2 1 a2 1 a3 1 a33 14

DB_AUTO_COMMIT
If set, operations for which no explicit transaction handle was specified, and which modify databases in the database environment, will be automatically enclosed within a transaction. If the call succeeds, changes made by the operation will be recoverable. If the call fails, the operation will have made no changes.

Calling DB_ENV->set_flags with the DB_AUTO_COMMIT flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_AUTO_COMMIT flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_AUTO_COMMIT flag may be used to configure Berkeley DB at any time during the life of the application. d36 8 a43 10 basis rather than on a per-database basis.

Calling DB_ENV->set_flags with the DB_CDB_ALLDB flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_CDB_ALLDB flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_CDB_ALLDB flag may be used to configure Berkeley DB only before the DB_ENV->open interface is called. a44 24

DB_DIRECT_DB
If set and supported by the system, Berkeley DB will turn off system buffering of Berkeley DB database files to avoid double caching.

Calling DB_ENV->set_flags with the DB_DIRECT_DB flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_DIRECT_DB flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_DIRECT_DB flag may be used to configure Berkeley DB at any time during the life of the application.

DB_DIRECT_LOG
If set and supported by the system, Berkeley DB will turn off system buffering of Berkeley DB log files to avoid double caching.

Calling DB_ENV->set_flags with the DB_DIRECT_LOG flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_DIRECT_LOG flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_DIRECT_LOG flag may be used to configure Berkeley DB at any time during the life of the application. d48 3 a50 6

Calling DB_ENV->set_flags with the DB_NOLOCKING flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle).

The DB_NOLOCKING flag may be used to configure Berkeley DB at any time during the life of the application. d53 1 a53 1 description of the DB_ENV->set_mp_mmapsize method for further d55 6 a60 10

Calling DB_ENV->set_flags with the DB_NOMMAP flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_NOMMAP flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_NOMMAP flag may be used to configure Berkeley DB at any time during the life of the application. d65 3 a67 17

Calling DB_ENV->set_flags with the DB_NOPANIC flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle).

The DB_NOPANIC flag may be used to configure Berkeley DB at any time during the life of the application.

DB_OVERWRITE
Overwrite files stored in encrypted formats before deleting them. Berkeley DB overwrites files using alternating 0xff, 0x00 and 0xff byte patterns. For file overwriting to be effective, the underlying file must be stored on a fixed-block filesystem. Systems with journaling or logging filesystems will require operating system support and probably modification of the Berkeley DB sources.

Calling DB_ENV->set_flags with the DB_OVERWRITE flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle).

The DB_OVERWRITE flag may be used to configure Berkeley DB at any time during the life of the application. d74 3 a76 6

Calling DB_ENV->set_flags with the DB_PANIC_ENVIRONMENT flag affects the database environment, including all threads of control accessing the database environment.

The DB_PANIC_ENVIRONMENT flag may be used to configure Berkeley DB at any time during the life of the application. d86 22 a107 49

Calling DB_ENV->set_flags with the DB_REGION_INIT flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_REGION_INIT flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_REGION_INIT flag may be used to configure Berkeley DB at any time during the life of the application.

DB_TXN_NOSYNC
If set, Berkeley DB will not write or synchronously flush the log on transaction commit or prepare. This means that transactions exhibit the ACI (atomicity, consistency, and isolation) properties, but not D (durability); that is, database integrity will be maintained, but if the application or system fails, it is possible some number of the most recently committed transactions may be undone during recovery. The number of transactions at risk is governed by how many log updates can fit into the log buffer, how often the operating system flushes dirty buffers to disk, and how often the log is checkpointed

Calling DB_ENV->set_flags with the DB_TXN_NOSYNC flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_TXN_NOSYNC flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_TXN_NOSYNC flag may be used to configure Berkeley DB at any time during the life of the application.

DB_TXN_WRITE_NOSYNC
If set, Berkeley DB will write, but will not synchronously flush, the log on transaction commit or prepare. This means that transactions exhibit the ACI (atomicity, consistency, and isolation) properties, but not D (durability); that is, database integrity will be maintained, but if the system fails, it is possible some number of the most recently committed transactions may be undone during recovery. The number of transactions at risk is governed by how often the system flushes dirty buffers to disk and how often the log is checkpointed.

Calling DB_ENV->set_flags with the DB_TXN_WRITE_NOSYNC flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_TXN_WRITE_NOSYNC flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_TXN_WRITE_NOSYNC flag may be used to configure Berkeley DB at any time during the life of the application. d111 5 a115 9

Calling DB_ENV->set_flags with the DB_YIELDCPU flag only affects the specified DB_ENV handle (and any other Berkeley DB handles opened within the scope of that handle). For consistent behavior across the environment, all DB_ENV handles opened in the environment must either set the DB_YIELDCPU flag or the flag should be specified in the DB_CONFIG configuration file.

The DB_YIELDCPU flag may be used to configure Berkeley DB at any time during the life of the application. d117 1 a117 1

The DB_ENV->set_flags method returns a non-zero error value on failure and 0 on success. d126 1 a126 1

The DB_ENV->set_flags method may fail and return a non-zero error for the following conditions: d130 4 a133 6

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

Class

DB_ENV d135 24 a158 1 Database Environments and Related Methods @