DB->close
DB->close |
|
#include <db.h>int DB->close(DB *db, u_int32_t flags);
The DB->close function flushes any cached database information to disk, closes any open cursors, frees any allocated resources, and closes any underlying files. Because key/data pairs are cached in memory, failing to sync the file with the DB->close or DB->sync function may result in inconsistent or lost information.
The flags value must be set to 0 or the following value:
It is important to understand that flushing cached information to disk only minimizes the window of opportunity for corrupted data. Although unlikely, it is possible for database corruption to happen if a system or application crash occurs while writing data to the database. To ensure that database corruption never occurs, applications must either: use transactions and logging with automatic recovery; use logging and application-specific recovery; or edit a copy of the database, and once all applications using the database have successfully called DB->close, atomically replace the original database with the updated copy.
When multiple threads are using the Berkeley DB handle concurrently, only a single thread may call the DB->close function.
After DB->close has been called, regardless of its return, the DB handle may not be accessed again.
The DB->close function returns a non-zero error value on failure, 0 on success, and returns DB_INCOMPLETE if the underlying database still has dirty pages in the cache. (The only reason to return DB_INCOMPLETE is if another thread of control were writing pages in the underlying database file at the same time as the DB->close function was called. For this reason, a return of DB_INCOMPLETE can normally be ignored; or, in cases where it is a possible return value, the DB_NOSYNC option should probably have been specified.)
The DB->close 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->close function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
|
|
Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @d1 1 a1 1 @ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d1 1 a1 1 d55 1 a55 1 DB handle may not be accessed again. @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 3 a3 1 d28 1 a28 1
The DB->close method flushes any cached database information to disk, d31 1 a31 1 to sync the file with the DB->close or DB->sync method may d33 2 a34 2
The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more of the following values: d52 13 a64 5
When multiple threads are using the DB concurrently, only a single thread may call the DB->close method.
The DB handle may not be accessed again after DB->close is called, regardless of its return.
The DB->close method returns a non-zero error value on failure and 0 on success. d66 4 a69 10
The DB->close method may fail and return a non-zero error for the following conditions:
The DB->close 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->close method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
The DB->close function flushes any cached database information to disk, d33 1 a33 1 to sync the file with the DB->close or DB->sync function may d35 2 a36 2
The flags value must be set to 0 or the following value: d54 5 a58 13
When multiple threads are using the Berkeley DB handle concurrently, only a single thread may call the DB->close function.
After DB->close has been called, regardless of its return, the DB handle may not be accessed again.
The DB->close function returns a non-zero error value on failure, 0 on success, and returns DB_INCOMPLETE if the underlying database still has dirty pages in the cache. (The only reason to return DB_INCOMPLETE is if another thread of control were writing pages in the underlying database file at the same time as the DB->close function was called. For this reason, a return of DB_INCOMPLETE can normally be ignored; or, in cases where it is a possible return value, the DB_NOSYNC option should probably have been specified.) d60 10 a69 4
The DB->close 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->close function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way. d71 1 a71 46 db_create, DB->associate, DB->close, DB->cursor, DB->del, DB->err, DB->errx DB->fd, DB->get, DB->pget, DB->get_byteswapped, DB->get_type, DB->join, DB->key_range, DB->open, DB->put, DB->remove, DB->rename, DB->set_alloc, DB->set_append_recno, DB->set_bt_compare, DB->set_bt_minkey, DB->set_bt_prefix, DB->set_cachesize, DB->set_dup_compare, DB->set_errcall, DB->set_errfile, DB->set_errpfx, DB->set_feedback, DB->set_flags, DB->set_h_ffactor, DB->set_h_hash, DB->set_h_nelem, DB->set_lorder, DB->set_pagesize, DB->set_paniccall, DB->set_q_extentsize, DB->set_re_delim, DB->set_re_len, DB->set_re_pad, DB->set_re_source, DB->stat, DB->sync, DB->truncate, DB->upgrade, and DB->verify. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 3 a3 1 d28 1 a28 1
The DB->close method flushes any cached database information to disk, d31 1 a31 1 to sync the file with the DB->close or DB->sync method may d33 2 a34 2
The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more of the following values: d52 13 a64 5
When multiple threads are using the DB concurrently, only a single thread may call the DB->close method.
The DB handle may not be accessed again after DB->close is called, regardless of its return.
The DB->close method returns a non-zero error value on failure and 0 on success. d66 4 a69 10
The DB->close method may fail and return a non-zero error for the following conditions:
The DB->close 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->close method may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.