On 20.04.2016 10:58, Michael Paquier wrote:
> On Wed, Apr 20, 2016 at 4:43 PM, Alex Ignatov <a.ignatov@postgrespro.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.
WALs also has performance issue. But we have it by default on minimal
level.
We also have CRC on WALs which also have performance hit.
--
Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
