Re: xapian-check sorted order error
Matthew Somerville <[email protected]> Thu, 22 Oct 2020 17:18:23 +0100
| Newsgroups | gmane.comp.search.xapian.general |
|---|---|
| Message-ID | <CAKs8PY3r03DGuRXFL5=uic67ZRr0Po3STtyFO_y_-4MknYSVTA@mail.gmail.com> |
On Wed, 21 Oct 2020 at 23:48, Olly Betts <[email protected]> wrote: > You may be able to fix it using "xapian-compact" as that walks all the > leaf items items in each table and writes them to new tables in a new > database - that will put the items back in the right order in the new > database, so if that's the only problem then that should fix it. Thanks for your reply. Sadly, xapian-compact gave the following output: postlist: Reduced by 29% 2026096K (6760968K -> 4734872K) record: Reduced by 2% 11968K (482040K -> 470072K) termlist: Reduced by 14% 1214720K (8408144K -> 7193424K) position ...terminate called after throwing an instance of 'std::length_error' what(): basic_string::_M_replace Aborted Guess to be on the safe side we'll look at scheduling in a full reindex, and add xapian-check to our backup script so it warns us if something like this happens again in future. ATB, Matthew