Re: M3 ahead...

subversion-dev@thewrittenword.com writes:
> Taking a brief look at the subversion code, you use Berkeley DB
> transactions though I don't see any evidence of Berkeley DB locks in
> libsvn_fs/.

Transactions use locks implicitly.

> Unless you're doing locking, I think the chances for encountering
> DB_RUN_RECOVERY are minimal. What does subversion do if a
> transaction has begun (txn_begin) and a signal interrupts the server
> before txn_commit() or txn_abort()?

Whatever resources were held by that transaction hang around, locked,
indefinitely, until they're cleaned up. Since Berkeley DB has no
reliable way to know when a database client has exited, it can't clean
up after it. The parent process (Apache) needs to notice when
children die ungracefully, and clean up.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:35 2006