4 ms·
FWIW, PG's default has been flipped to checksums being enabled by default in the in-development version. Personally I'm not sure it's the right call, as it com
by anarazel 2y ago
FWIW, PG's default has been flipped to checksums being enabled by default in the in-development version.
Personally I'm not sure it's the right call, as it comes with some increased write overhead.
- aflukasz 2y agoYes, it's a balancing act. I think it's better to have safer defaults here, not prioritizing extra performance. People who are concerned with performance to the degree where checksums would matter need to consult configuration anyway (in many aspects, not only this one) and can disable this specific thing easily. For the reference, change is in https://github.com/postgres/postgres/commit/04bec894a04cb0d32533f1522ab81b7016141ff1 https://github.com/postgres/postgres/commit/04bec894a04cb0d3... (so should land in PostgreSQL 18 in a year, unless it will get reverted for some reason).