Re: data checksums
От | Laurenz Albe |
---|---|
Тема | Re: data checksums |
Дата | |
Msg-id | 830004cb0a514d803d13ab9abcfa15fbae365748.camel@cybertec.at обсуждение исходный текст |
Ответ на | Re: data checksums (Christophe Pettus <xof@thebuild.com>) |
Ответы |
Re: data checksums
|
Список | pgsql-general |
On Tue, 2024-08-06 at 09:29 -0700, Christophe Pettus wrote: > > > On Aug 6, 2024, at 08:11, bruno vieira da silva <brunogiovs@gmail.com> wrote: > > > > so my question is why data checksums aren't enabled by default on pg? > > At this point, mostly historical reasons. They're also superfluous if your underlying > file system or storage hardware does storage-level corruption checks (which most don't). I am surprised by that. Would you say that most storage systems will happily give you a garbage block if there was a hardware problem somewhere? > > the pg doc > > mentions a considerable performance penality, how considerable it is? > > That line is probably somewhat out of date at this point. We haven't seen a significant > slowdown in enabling them on any modern hardware. I always turn them on, except on the > type of filesystems/hardware mentioned above. Turning data checksums on will write WAL for hint bits, which can significantly increase the amount of WAL written. Yours, Laurenz Albe
В списке pgsql-general по дате отправления: