Re: svn commit: rev 5361 - trunk/subversion/mod_dav_svn

Philip Martin wrote:

>Branko ÄŒibej <brane@xbc.nu> writes:
>
>
>
>>So I suggest we put the UUID in a file *in addition* to its being
>>stored in a table. There'd be some work involved in maintaining that
>>value (e.g., "svnadmin create" and "svnadmin load" would have to
>>copy it out of the table in the FS), but I think that's not too
>>hard.
>>
>>
>
>Can the update process be atomic? Suppose a process is interrupted
>while setting the UUID. Subversion really ought be able to guarantee
>that the UUID has either been changed to the new value or remains
>unaltered.
>
>I suppose we could use rules that allow the file, say, to be optional.
>Then the update process is delete the file, update the table, create a
>new file. Essentially the file is an optional cache of the value in
>the table.
>
>

You really don't change the repository UUID all that often. The only
operations I can think of that do that are "svnadmin create" and
"svnadmin load", and whatever mechanism is below that. And those
operations are exclusive-access only.

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org