[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: M3 ahead...

From: <subversion-dev_at_thewrittenword.com>
Date: 2001-08-04 08:30:58 CEST

On Fri, Aug 03, 2001 at 11:36:04PM -0500, Jim Blandy wrote:
> subversion-dev@thewrittenword.com writes:
> > 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.

And how does Apache find out about the transaction ID that is needed
by txn_abort()? Does mod_dav_svn have this info?

albert chin (china@thewrittenword.com)
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

This is an archived mail posted to the Subversion Dev mailing list.