| From: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Initdb --data-checksums by default |
| Date: | 2016-04-20 07:43:43 |
| Message-ID: | 5717332F.3020709@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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?
--
Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2016-04-20 07:47:10 | Re: Initdb --data-checksums by default |
| Previous Message | Albe Laurenz | 2016-04-20 07:41:41 | Re: How do BEGIN/COMMIT/ABORT operate in a nested SPI query? |