I've updated http://crbug.com/25959 with some comments.
The suggestion was made to exclude the entire profile directory as a
short-term solution, but that would mean not backing up the bookmarks
and cookies. So for the immediate need (M4) what is more important:
a) saving space in the Time
On Tue, Nov 10, 2009 at 08:14, mrossetti mrosse...@chromium.org wrote:
I've updated http://crbug.com/25959 with some comments.
The suggestion was made to exclude the entire profile directory as a
short-term solution, but that would mean not backing up the bookmarks
and cookies. So for the
I've verified with SQLite that journal files do NOT get the sync cookie.
We could consider adding it to our SQLite, I suppose. It looks like
there is room in the journal header for things like that. Not sure
how often it comes up, but if it does come up it would be pretty
devastating.
-scott
On Nov 6, 2009, at 10:09 AM, mrossetti wrote:
1) Exclude individual database files. Journal files would still be
backed up.
2) Move the database files into a new, excluded directory. Both the
database files and their journals would not be backed up.
By 'journal' do you mean the temporary
Applying incorrect journal files would be bad. SQLite uses a sync
cookie to do some tricks WRT keeping the cache warm. I'm somewhat
surprised that the same thing isn't used to prevent applying journal
files inappropriately.
[I don't know this, and should not be spending time verifying it just
