| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Greg Burd <greg(at)burd(dot)me>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Tomas Vondra <tomas(at)vondra(dot)me>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, Michael Banck <mbanck(at)gmx(dot)net>, Jeff Davis <pgsql(at)j-davis(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Enable data checksums by default |
| Date: | 2025-07-31 20:42:26 |
| Message-ID: | CAKAnmmKEDYFJ17qtPpEOF98NMcCxB-ZsVW4OCG8f3p7XSGrHGQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 31, 2025 at 3:21 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> Having checksums on does not improve data integrity...
>
Maybe not directly, but in the same way that a smoke detector does not
directly prevent fire damage. Checksums do allow you to detect problems and
fix things (esp. bad hardware) before they get worse.
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-07-31 21:24:38 | Re: Improve LWLock tranche name visibility across backends |
| Previous Message | Corey Huinker | 2025-07-31 20:28:08 | Re: pg_dump --with-* options |