The database currently uses character varying (255) fields for checksums and stores checksums as a hexidecimal string representation. It would make more sense to use a bytea field instead as this data is just a binary field of a certain length (depending on the type of checksum algorithm used). This would result in around half the memory usage for these checksum fields.