[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Does fsfs revprop packing no longer allow usage of traditional backup software?

From: <kmradke_at_rockwellcollins.com>
Date: Thu, 30 Jun 2011 13:46:46 -0500

Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote on 06/30/2011 01:41:51 PM:
> > >> The reason SQLite was used is that rev props can be edited via svn
> > >> prop*--revprop
> > >>
> > >> So you could also disable the pre-revprop-change hook during a
> > >> and that should make you safe. And if you have not enabled it in
> > >> first place, then there is really no issue anyway.
> > >>
> > >
> > > Inaccurate.
> > >
> > > The pre-revprop-change hook lives in libsvn_repos. It has zero
> > > on API users that change revprop via libsvn_fs API's.
> >
> > OK, then what is accurate? Are you saying we do not support editing
> > revision properties once they are packed? Is the SQLite db that
> > stores revprops only written to by the pack process?
> It is possible to edit revprops both before and after 'svnadmin pack'.
> In the 'after' case, a non-svn_fs_pack() process modifies revprops.db
> in-place.

I'm still not clear if a single .db file is used once a repo is packed,
or if that .db file only holds the "packed" revprops and not the
currently "unpacked" ones.

Or asked a different way, does a new commit update the revprop.db or
does it just create files like 1.6 did and things are only added
to the db during svnadmin pack...

Kevin R.
Received on 2011-06-30 20:47:21 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.