Bug#724610: Acknowledgement (incrementally updated databases eventually become corrupt)

[Olly Betts]

reassign 724610 src:xapian-core 1.2.15-2
thanks

On Wed, Sep 25, 2013 at 06:20:11PM -0400, Joey Hess wrote:
> Archive of complete database: http://tmp.kitenet.net/xapian-1.tar.bz2

OK, so there's a bug in xapian-check - if a commit operation was
interrupted, then there can be a partial set of base files for the new
revision.  Opening the database carefully looks for a set of base files
at the same revision, but checking only opens the latest revision for
each table, which means it can pick up some old ones and some new ones
and report problems when there aren't actually any.

I have fixed this in upstream trunk - with this fixed your database above
passes xapian-check.

I'm working on backporting this fix to 1.2, but it's a bit tricky to
do - I need to get at the database revision number from the checking code,
which is easy on trunk as the checking code is in libxapian, but in 1.2
it was outside the library so it can't access the database internals.
So I don't have a patch for which is usable in the debian package yet.

I think there's another issue here though, as this xapian-check problem
doesn't explain the error here:

http://www.branchable.com/bugs/Exception:_Cannot_open_tables_at_consistent_revisions_at___47__usr__47__lib__47__perl5__47__Search__47__Xapian__47__WritableDatabase.pm_line_41./#comment-c159ea3f9be35fcd9ed0eeedb162e816

Are you able to supply a copy of a database exhibiting the "Cannot open
tables at consistent revisions" error?

Cheers,
    Olly