Comment 1 for bug 797238

Evergreen won't ever re-ingest a deleted record. Once deleted the last state is essentially written in stone. If you undelete it, it will be re-ingested, though.

Also, note that updating a record to save a few bytes by removing a tag will actually end up using more space, for two reason: the auditor table gets a new row, and the old row will still be in the table taking up space until that specific space is reclaimed by a subsequent vacuum. If space savings is the primary reason for including deleted records in the update, it's actually better and (in light of the above intended skipping of deleted records during re-ingest) more correct thing to do.

As for cleaning up metabib.full_rec, changing the data there would be counter-productive as reports expect to be able to pull information on "deleted" records from the super-simple record extracts view (in a "at the time of deletion" state).

--miker