Op Ma, 25 januari, 2010 08:18, schreef Paul Serice:
On Sun, 2010-01-24 at 18:29 -0500, D. Richard Hipp wrote:
On Jan 24, 2010, at 5:42 PM, Paul Serice wrote:
Just search for Berkeley DB usage leading to respository
corruption and data loss on the Wikipedia page for Subversion.
That's why
I took a look at subversion, and it seems to use a single db/filesystem FSFS?
I'm guessing the same issues apply?
Cheers,
Stephen
On Friday, January 22, 2010, Stephen De Gabrielle
stephen.degabrie...@acm.org wrote:
Hi someone recently mentioned to me that they were uncomfortable with
their
Stephen De Gabrielle wrote:
I took a look at subversion, and it seems to use a single db/filesystem FSFS?
I'm guessing the same issues apply?
Hmmm ... at least if using the FSFS storage, a repository consists of a
lot of files. They can be backed up very comfortably as they are
immutable
On Sun, 2010-01-24 at 15:35 -0500, D. Richard Hipp wrote:
Could this be a case of we've never done it that way before?
I think it's more a case of been there, done that, never want to do
it again. Just search for Berkeley DB usage leading to respository
corruption and data loss on the Wikipedia
Hi someone recently mentioned to me that they were uncomfortable with
their entire repository in a single file. I am happy with it, but why
would this be a problem?
-Large projects?
-Big blobs in your source?
-filesystem limits
-lots of submitters (eg git for the Linux kernel)
I'd like to come up
5 matches
Mail list logo
