#include <db.h> int DB_ENV->log_get_config(DB_ENV *dbenv, u_int32_t which, int *onoffp);
The DB_ENV->log_get_config()
method returns whether the specified
which parameter is currently set or
not. You can manage this value using the
DB_ENV->log_set_config()
method.
The DB_ENV->log_get_config()
method may be called at any time during
the life of the application.
The DB_ENV->log_get_config()
method returns a non-zero error value on failure and 0 on success.
The which parameter is the message value for which configuration is being checked. Must be set to one of the following values:
Enables full logging of external file data.
System buffering is turned off for Berkeley DB log files to avoid double caching.
Berkeley DB is configured to flush log writes to the backing disk before returning from the write system call, rather than flushing log writes explicitly in a separate system call, as necessary.
Berkeley DB automatically removes log files that are no longer needed.
Transaction logs are maintained in memory rather than on disk. This means that transactions exhibit the ACI (atomicity, consistency, and isolation) properties, but not D (durability).
The transaction log is not flushed from from the operating system cache to stable storage when the logging system switches log files or a durable transaction commits. This means that transactions exhibit the ACI (atomicity, consistency, and isolation) properties, but only partially support D (durability); that is, database integrity will be maintained if the application fails and the environment is recovered, but not if the system fails. All database files must be verified and/or restored from a replication group master or archival backup after system failure.
All pages of a log file are zeroed when that log file is created.