From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Checksums by default? |
Date: | 2017-01-25 19:23:46 |
Message-ID: | 20170125192346.GO9812@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert,
* Robert Haas (robertmhaas(at)gmail(dot)com) wrote:
> On Wed, Jan 25, 2017 at 12:02 AM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> > I'm not completely grokking your second paragraph, but I would think that an
> > average user would love got get a heads-up that their hardware is failing.
>
> Sure. If the database runs fast enough with checksums enabled,
> there's basically no reason to have them turned off. The issue is
> when it doesn't.
I don't believe we're talking about forcing every user to have checksums
enabled. We are discussing the default.
Would you say that most user's databases run fast enough with checksums
enabled? Or more than most, maybe 70%? 80%? In today's environment,
I'd probably say that it's more like 90+%.
Yet, our default is to have them disabled and *really* hard to enable.
I agree that it's unfortunate that we haven't put more effort into
fixing that- I'm all for it, but it's disappointing to see that people
are not in favor of changing the default as I believe it would both help
our users and encourage more development of the feature.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-01-25 19:24:09 | Re: Checksums by default? |
Previous Message | Robert Haas | 2017-01-25 19:19:23 | Re: pg_ls_dir & friends still have a hard-coded superuser check |