| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | BGoebel <b(dot)goebel(at)prisma-computer(dot)de>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Using of --data-checksums |
| Date: | 2020-04-10 20:25:08 |
| Message-ID: | 20200410202508.GB24987@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Apr 8, 2020 at 11:54:34AM -0400, Stephen Frost wrote:
> Greetings,
>
> * BGoebel (b(dot)goebel(at)prisma-computer(dot)de) wrote:
> > initdb --data-checksums "... help to detect corruption by the I/O system"
> > There is an (negligible?) impact on performance, ok.
> >
> > Is there another reason NOT to use this feature ?
>
> Not in my view.
>
> > Has anyone had good or bad experience with the use of --data-checksums?
>
> Have had good experience with it. We should really make it the default
> already.
Yeah, but I think we wanted more ability to change an existing cluster
before doing that since it would affect pg_upgraded servers.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-04-10 20:37:46 | Re: Using of --data-checksums |
| Previous Message | Andrus | 2020-04-10 20:20:04 | Forcibly disconnect users from one database |