Re: #739: Ensuring ACID in Subversion (aka watcher procecesses are fun)

"Bill Tutt" <rassilon@lyra.org> writes:

> > You are seriously proposing a root process that kills other processes?
> > Including my Subversion aware editor which happens to be accessing the
> > repository? And my debugging session which happens to have reused the
> > crashed Subversion client process ID? This is a "completely and
> > utterly robust" solution?
>
> Well, we must do something.
>
> Alternative suggestions that do solve the problem are certainly
> welcomed.

It depends on how you define "completely and utterly robust" :-)

Having all the clients receive SVN_ERR_REPOS_RECOVER and print
"repository /foo/bar/repo requires recovery" and relying on the
repository administrator running db_recover would do for me.

At present, ra_local never loses data once it has been committed, it
is "completely and utterly robust". All I want is to minimise the
circumstances that cause SVN_ERR_REPOS_RECOVER. But when it does
occur I am happy with manual intervention.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org