Comment 6 for bug 882502

Revision history for this message
Chris Rossi (chris-archimedeanco) wrote :

I've done some poking around in production and what I've found is that the specific type of corruption detected and fixed by evolve11 isn't happening here. This script looks look at all of the document map entries and makes sure all of those entries actually match up to an object in the database. I just run a variant of that script in production just to check the document map's integrity, without actually fixing anything. What I've found is that there is no problem there.

There must, then, be an index (or indexes) which have entries for documents that are no longer in the system. To check for that we'd need to look at all of the document ids in all of the indexes and see whether they correspond to a document in the system. Although in newer versions of repoze.catalog there is a uniform API for getting all of the docids in an index, we're still using a version of repoze.catalog which lacks that API, so it'll take an hour or two for me to write a script to do this check, probably.