Re: svn commit: r33724 - branches/fsfs-pack/subversion/libsvn_fs_fs

On Sat, Oct 18, 2008 at 6:24 AM, Hyrum K. Wright
<hyrum_wright_at_mail.utexas.edu> wrote:
> Greg Stein wrote:
>> Since you've already added sqlite, then you can simply go another
>> step: put the revprops in there. (I'd suggest as a separate dev effort
>> tho)
>
> That was my thought exactly (same with the fsfs locks storage, too). My only
> concerns are scalability and consistency on something like NFS. If we lose data
> from the rep-cache sqlite database, that doesn't impact the correctness of the
> repository. If something happens to revprops, it's a different story.

I seem to recall that Kamesh had started a branch for storing revprops
in SQLite back when we were doing 1.5 and SQLite was part of the
repository. I do not see a branch though so I am not sure if it was
deleted when we purged SQLite from the repository or perhaps he just
never got started with it.

The pack idea certainly becomes less useful without doing the revprops
as they were likely going to give the biggest space savings on
average. Of course if the revprops wind up in something like SQLite
you will not need to use pack to get that savings.

Finally, on the locking concerns you post for SQLite, I was under the
impression that fsfs itself had the same requirements and would also
have problems on buggy NFS implementations.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org