| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Greg Sabino Mullane <htamfids(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Enable data checksums by default |
| Date: | 2024-08-08 17:42:55 |
| Message-ID: | CA+TgmoZjvCnFuQR5MnGkr9A7yYNArSFbUtrjhoD60U2iaMj-Vw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 8, 2024 at 6:11 AM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> About the claim that it's already the de-facto standard. Maybe that is
> approximately true for "serious" installations. But AFAICT, the popular
> packagings don't enable checksums by default, so there is likely a
> significant middle tier between "just trying it out" and serious
> production use that don't have it turned on.
+1.
> I'm thinking pg_upgrade could have a mode where it adds the
> checksum during the upgrade as it copies the files (essentially a subset
> of pg_checksums). I think that would be useful for that middle tier of
> users who just want a good default experience.
That would be very nice.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-08-08 17:51:32 | fix CRC algorithm in WAL reliability docs |
| Previous Message | Robert Haas | 2024-08-08 17:25:47 | Re: Vectored IO in XLogWrite() |