Fix "xapian audit creates a bogus directory with no entries" bug #5014
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This caused real production issues at Fastmail. We have a weekly cronjob running
squatter -A
to audit indexes. This creates a zero-record database, which when you later try to open it causes issues!The fix is to check that we got all the expected Xapian glass files before considering a database to be "real", and so we don't include databases without terms.
This really is a multi-stage bug! Stage 1:
Still works - but then we use compact_dbs to compact that empty database, and it produces a broken database!
But then we compact that one down, and:
and in syslog: