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.55.13; author rse; state dead;
branches;
next 1.1;
commitid z4cpSiAhOCXk5PLs;
1.1
date 2001.07.23.20.45.37; author rse; state Exp;
branches
1.1.1.1;
next ;
1.1.1.1
date 2001.07.23.20.45.37; author rse; state Exp;
branches;
next 1.1.1.2;
1.1.1.2
date 2002.01.08.00.30.12; author rse; state Exp;
branches;
next 1.1.1.3;
1.1.1.3
date 2003.01.18.13.49.02; author rse; state Exp;
branches;
next 1.1.1.4;
1.1.1.4
date 2001.05.13.19.58.45; author rse; state Exp;
branches;
next 1.1.1.5;
1.1.1.5
date 2003.01.18.14.05.00; author rse; state Exp;
branches;
next ;
desc
@@
1.2
log
@remove the ancient RPM 4.2.1 source tree copy
@
text
@
Berkeley DB Reference Guide: What other services does Berkeley DB provide?
- Berkeley DB Reference Guide:
- Introduction
|
  
|
What other services does Berkeley DB provide?
Berkeley DB also provides core database services to developers. These
services include:
- Page cache management:
- The page cache provides fast access to a cache of database pages,
handling the I/O associated with the cache to ensure that dirty pages
are written back to the file system and that new pages are allocated on
demand. Applications may use the Berkeley DB shared memory buffer manager to
serve their own files and pages.
- Transactions and logging:
- The transaction and logging systems provide recoverability and atomicity
for multiple database operations. The transaction system uses two-phase
locking and write-ahead logging protocols to ensure that database
operations may be undone or redone in the case of application or system
failure. Applications may use Berkeley DB transaction and logging subsystems
to protect their own data structures and operations from application or
system failure.
- Locking:
- The locking system provides multiple reader or single writer access to
objects. The Berkeley DB access methods use the locking system to acquire
the right to read or write database pages. Applications may use the
Berkeley DB locking subsystem to support their own locking needs.
By combining the page cache, transaction, locking, and logging systems,
Berkeley DB provides the same services found in much larger, more complex and
more expensive database systems. Berkeley DB supports multiple simultaneous
readers and writers and guarantees that all changes are recoverable, even
in the case of a catastrophic hardware failure during a database update.
Developers may select some or all of the core database services for any
access method or database. Therefore, it is possible to choose the
appropriate storage structure and the right degrees of concurrency and
recoverability for any application. In addition, some of the subsystems
(for example, the Locking subsystem) can be called separately from the
Berkeley DB access method. As a result, developers can integrate non-database
objects into their transactional applications using Berkeley DB.
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
@
1.1.1.3
log
@Import: RPM 4.0.5
@
text
@d2 1
a2 1
a3 1
@
1.1.1.4
log
@Import: RPM 4.1
@
text
@d2 1
a2 1
d4 1
@
1.1.1.5
log
@Import: RPM 4.1.1
@
text
@d2 1
a2 1
a3 1
@