Re: data-checksums

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Rakesh Kumar <rakeshkumar464(at)mail(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: data-checksums
Date: 2018-01-09 17:54:10
Message-ID: 20180109175410.GH2416@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Greetings,

* Rakesh Kumar (rakeshkumar464(at)mail(dot)com) wrote:
> --data-checksums
> Use checksums on data pages to help detect corruption by the I/O system that would otherwise be silent. Enabling checksums may incur a noticeable performance penalty. This option can only be set during initialization, and cannot be changed later. If set, checksums are calculated for all objects, in all databases.
> ====
>
> If I understand it correctly, the performance penalty is when the blocks are written to the disk by the background writer and/or during checkpoint. Given that the process is async and application does not wait on it, is the performance penalty really a big concern.

There's also a hit when pages are read back in, since we need to
calculate the checksum and verify it hasn't changed.

That said, imv anyway, the performance hit is small and having checksums
is well worth it.

Thanks!

Stephen

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rakesh Kumar 2018-01-09 17:58:41 Re: data-checksums
Previous Message Rakesh Kumar 2018-01-09 17:42:07 data-checksums