[Date Prev][Date Next]
Re: index corruption (1164) still present in 2.0.15 with db 3.1.17 (ITS#1359)
At 10:39 AM 2001-09-29, email@example.com wrote:
>The good news is that there was no index curruption with gdbm!
Yes, the problems appear to be limited to use of Berkeley
DB's Concurrent DB API.
>I will try a db-3.3.11 version of ldbm now and report back.
If you have problems, try undefining HAVE_BERKELEY_DB_THREAD
(portable.h). This will disable use of the Concurrent DB API
and should resolve the problem (at the expense of concurrency).