[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: HAVE_BERKELEY_DB_THREAD (ITS#1176)
> At 08:48 AM 5/28/01, bostic@sleepycat.com wrote:
>>Since OpenLdap doesn't support transactions yet, my guess is
>>that it shouldn't be permitting multiple threads of control to
>>access the database, as long as there's at least one writer
>>thread. Under high levels of concurrency, when deadlock can
>>occur, the database may become corrupted.
>
> Can DB deadlock occur when no DB write cursors are used?
Yes; page splits can result in deadlock for even non-cursor
operations. (This situation has improved in the upcoming
Berkeley DB 3.3.XX release, but in general, applications that
allow more than a single-thread of control into the database
should be prepared to handle deadlock.)
Regards,
--keith
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Keith Bostic
Sleepycat Software Inc. bostic@sleepycat.com
118 Tower Rd. +1-781-259-3139
Lincoln, MA 01773 http://www.sleepycat.com