| From: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Initdb --data-checksums by default |
| Date: | 2016-04-20 15:05:19 |
| Message-ID: | 57179AAF.5080502@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 20.04.2016 16:58, Alvaro Herrera wrote:
> 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.
>
Right now i am working on this tests. On various media - hdd ssd ram and
some various workload. As soon as results be ready i'll provide my numbers
--
Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2016-04-20 15:38:16 | Re: Enhancement Request |
| Previous Message | Tom Lane | 2016-04-20 14:28:33 | Re: How do BEGIN/COMMIT/ABORT operate in a nested SPI query? |