Re: Initdb --data-checksums by default - Mailing list pgsql-general

From Andreas Joseph Krogh
Subject Re: Initdb --data-checksums by default
Date
Msg-id VisenaEmail.17.7ce0bf9558d0776c.15432d0a8a0@tc7-visena
Whole thread Raw
In response to Re: Initdb --data-checksums by default  (Alex Ignatov <a.ignatov@postgrespro.ru>)
Responses Re: Initdb --data-checksums by default
List pgsql-general
På onsdag 20. april 2016 kl. 10:33:14, skrev Alex Ignatov <a.ignatov@postgrespro.ru>:


On 20.04.2016 11:29, Devrim Gündüz wrote:
> Hi,
>
> On Wed, 2016-04-20 at 10:43 +0300, Alex Ignatov wrote:
>> 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?
> I think this should be discussed in -hackers, right?
>
> Regards,
May be you right but i want to know what people think about it before
i'll write to hackers.
 
-1 on changing the default.
 
10^15 ~= 1000 TB, which isn't very common yet. Those having it probably are aware of the risk and have enabled checksums already.
 
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
 
Attachment

pgsql-general by date:

Previous
From: "Shulgin, Oleksandr"
Date:
Subject: Re: Enhancement Request
Next
From:
Date:
Subject: Re: How do BEGIN/COMMIT/ABORT operate in a nested SPI query?