Edit File - File Manager

Edit File: cam_conv.html

<html>
<head>
<title>Berkeley DB Reference Guide: Berkeley DB Concurrent Data Store locking conventions</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<a name="2"></a>
<table width="100%"><tr valign=top>
<td><dl><dt>Berkeley DB Reference Guide:<dd>Locking Subsystem</dl></td>
<td align=right><a href="../lock/twopl.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../lock/am_conv.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Berkeley DB Concurrent Data Store locking conventions
The Berkeley DB Concurrent Data Store product has a simple set of conventions for locking. It
provides multiple-reader/single-writer semantics, but not per-page
locking or transaction recoverability. As such, it does its locking
entirely in the Berkeley DB interface layer.
The object it locks is the file, identified by its unique file number.
The locking matrix is not one of the two standard lock modes, instead,
we use a four-lock set, consisting of the following:
 
DB_LOCK_NG<ul compact><li>not granted (always 0)</ul>
DB_LOCK_READ<ul compact><li>read (shared)</ul>
DB_LOCK_WRITE<ul compact><li>write (exclusive)</ul>
DB_LOCK_IWRITE<ul compact><li>intention-to-write (shared with NG and READ, but conflicts with WRITE and IWRITE)</ul>
 
The IWRITE lock is used for cursors that will be used for updating
(IWRITE locks are implicitly obtained for write operations through the
Berkeley DB handles, for example, <a href="../../api_c/db_put.html">DB-&gt;put</a> or <a href="../../api_c/db_del.html">DB-&gt;del</a>). While
the cursor is reading, the IWRITE lock is held; but as soon as the
cursor is about to modify the database, the IWRITE is upgraded to a
WRITE lock. This upgrade blocks until all readers have exited the
database. Because only one IWRITE lock is allowed at any one time, no
two cursors can ever try to upgrade to a WRITE lock at the same time,
and therefore deadlocks are prevented, which is essential because Berkeley DB Concurrent Data Store
does not include deadlock detection and recovery.
Applications that need to lock compatibly with Berkeley DB Concurrent Data Store must obey the
following rules:
<ol>
<li>Use only lock modes DB_LOCK_NG, DB_LOCK_READ, DB_LOCK_WRITE,
DB_LOCK_IWRITE.
<li>Never attempt to acquire a WRITE lock on an object that is
already locked with a READ lock.
</ol>
<table width="100%"><tr><td> </td><td align=right><a href="../lock/twopl.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../lock/am_conv.html"><img src="../../images/next.gif" alt="Next"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

Back to File Manager