Comment 4 for bug 1091885

Still an issue in 3.1. What's happening is in the biblio.indexing_ingest_or_delete it's checking for the trigger to be an update and then when the MARC hasn't changed skipping re-ingest steps. By telling it to only check for MARC being the same when the old row deleted is FALSE it will have it re-ingest properly when being undeleted. There may be some edge cases where a few unnecessary ingests happen but if so it will be only if MARC blobs are being manipulated _and_ left deleted which seems ... unlikely.

Patch forthcoming.