"with possibly disastrous consequences for data durability/consistency (which is something the PostgreSQL community really values)." Do they though? Well, sur

"with possibly disastrous consequences for data durability/consistency (which is something the PostgreSQL community really values)." Do they though? Well, sure, they might value it, but do they prioritize it? E.g. checksums for data pages were only introduced in PostgreSQL 9.3 and they are still disabled by default today in PostgreSQL 14. That might be the right choice if your underlying filesystem provides checksums for content (e.g. ZFS) and memory is protected from corruption via other means (likely given on a DB server holding data someone cares about), but should that assumption be the default? See https://bsdmag.org/page-checksum-protection-in-postgresql/ https://bsdmag.org/page-checksum-protection-in-postgresql/