| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Michael Banck <michael(dot)banck(at)credativ(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, Stephen Frost <sfrost(at)snowman(dot)net>, 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 17:58:37 |
| Message-ID: | 20210106175837.be4cmj3b4ibzkipy@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2021-01-06 18:27:48 +0100, Magnus Hagander wrote:
> The other argument is that admins can cheaply and quickly turn off
> checksums if they don't want them.
>
> The same cannot be said for turning them *on* again, that's a very
> slow offline operation at this time.
>
> Turning off checksums doesn't take noticeably more time than say
> changing the shared_buffers from the default, which is also almost
> guaranteed to be wrong for most installations.
It still requires running a binary locally on the DB server, no? Which
means it'll not be an option on most cloud providers...
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2021-01-06 18:01:59 | Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help) |
| Previous Message | Andres Freund | 2021-01-06 17:55:08 | Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help) |