https://bugs.kde.org/show_bug.cgi?id=356357
--- Comment #3 from Riku Voipio <[email protected]> --- > I'm a little conflicted about this approach since when the index does get > corrupted, it will be impossible for us to detect it. I think it would better to work on detecting and recovering corruption. It's not like a system crash while indexing is the only way the DB can be corrupted. To take a page from the crash-only software ideology[1], the idea is to concentrate in solid recovery rather than preventing crashes and data corruption in first place. [1] https://lwn.net/Articles/191059/ -- You are receiving this mail because: You are watching all bug changes.
