> This problem appears to be mostly fixed as a practical concern (I think
> mostly by eliminating circumstances where rpm processes would exit
> uncleanly), but it's still symptomatic of Berkeley DB's brittleness when
> used as an embedded database.
I can't really let that one go. :-)
It is incorrect to say Berkeley DB is brittle when used as an
embedded database. I can point to a lot of high-end server
applications (Sun Microsystem's LDAP Directory Server, Google's
identity infrastructure, Amazon's launch pages, and many more),
all safely embedding Berkeley DB.
To use Berkeley DB, you have to conform to its requirements for
running database recovery -- which requirements are explicitly
documented. I'm happy to work with you to develop code that
allows Subversion to conform to those requirements, but to not
conform to the requirements and then complain that DB is brittle
when it fails, isn't reasonable.
Regards,
--keith
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Keith Bostic bostic@sleepycat.com
Sleepycat Software Inc. keithbosticim (ymsgid)
118 Tower Rd. +1-781-259-3139
Lincoln, MA 01773 http://www.sleepycat.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 13 16:50:19 2004