Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help)

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Michael Banck <michael(dot)banck(at)credativ(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help)
Date: 2021-01-06 19:53:39
Message-ID: CAH2-WzmWmcVTNr98Ot4ovcDMX0vW8D5248YCq3jcbZNFNar_LQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 6, 2021 at 11:44 AM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Having fsync off won't actually cause corruption unless you have an OS
> crash or don't sync the disks when you reboot the system though- so it's
> a hedge against certain failure conditions, as is checksums.

I find this argument baffling. Do you really believe this?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2021-01-06 20:03:04 Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help)
Previous Message Stephen Frost 2021-01-06 19:44:42 Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help)