A weird wordlist.db problem

[Matthias Andree]

Tom Eastman <tom at cs.otago.ac.nz> writes:

> Sorry for the rant, this is a few months after I switched all my subversion
> repositories over to fsfs because a similar problem ate all six of
> them. 

I don't think so. Berkeley DB for subversion should only corrupt if

1. you're running a broken (i. e. older) version,

2. you're updating Berkeley DB without dumping the database before the
   update and reloading it after the update.

> What is Berkeley db buying bogofilter?  It doesn't seem to be peace of
> mind.

Indeed it isn't - Berkeley DB has brought a lot of complexity but it's
one of the best documented and fastest databases we have found for
bogofilter.

For those who want solid databases, I recommend the latest 0.94.14
release and using transactional databases, see README.db for
instructions on upgrading an existing database to a transactional.

Alternatively, bogofilter can be compiled to use sqlite-3.2.0 or newer
(FreeBSD has a mail/bogofilter-sqlite port that you can install); you
must dump your existing databases *before* installing the sqlite
version, then remove and reload the databases after bogofilter-sqlite is
installed.

SQLite3 is easier to use than Berkeley DB IMO at an acceptable
performance disadvantage.

> Okay.. I'm calm again.  Is there really no way to repair the database? 

Read README.db. Note that your system may rename the utilities to
db43_dump, db_dump-4.3 or something like that, where 43 or 4.3 is the
Berkeley DB version without or with dot, and your distribution may
ship the utilities in a separate package, db-utils, db43-utils or
something like that.

-- 
Matthias Andree