| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Initdb --data-checksums by default |
| Date: | 2016-04-20 07:58:25 |
| Message-ID: | CAB7nPqTwHwETW4LYdWDE4WKkBDrPZtjjZzXngGv4Tx_t_YtrDg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 20, 2016 at 4:43 PM, Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> wrote:
> Hello everyone!
> Today in Big Data epoch silent data corruption becoming more and more issue
> to afraid of. With uncorrectable read error rate ~ 10^-15 on multiterabyte
> disk bit rot is the real issue.
> I think that today checksumming data must be mandatory set by default.
> Only if someone doesn't care about his data he can manually turn this option
> off.
>
> What do you think about defaulting --data-checksums in initdb?
Not sure that most users deploying Postgres by default are ready to
pay the price of data checksums in their default deployments. People
using it are already using the -k switch, so it may actually be a trap
to switch the default.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Ignatov | 2016-04-20 08:00:56 | Re: Initdb --data-checksums by default |
| Previous Message | John R Pierce | 2016-04-20 07:47:10 | Re: Initdb --data-checksums by default |