| From: | Alvaro Herrera <alvherre(at)2ndquadrant(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 13:58:08 |
| Message-ID: | 20160420135808.GA855511@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alex Ignatov 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.
In principle I support the idea of turning data checksums by default,
but can you provide some numbers on how it affects performance on
various workloads? That's a critical point in the discussion.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | david | 2016-04-20 14:17:00 | Re: How do BEGIN/COMMIT/ABORT operate in a nested SPI query? |
| Previous Message | Adrian Klaver | 2016-04-20 13:44:26 | Re: Initdb --data-checksums by default |