Staging instance, all changes can be removed at any time

drop blake2 hashes

Is there a point in keeping blake2 hashes in the content table?

With Git moving to SHA2[56] I don't see hash moving to blake2 anytime soon, and anyway it's always only been in the content table. Dropping blake2 will free up some DB space (once Postgres is able to reclaim it...) and reduce both CPU and IO time during ingestion.

Aside from the work needed to drop them, do we have any reason to keep blake2 hashes around?

Migrated from T2474 (view on Phabricator)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information