Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help)
От | Andres Freund |
---|---|
Тема | Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help) |
Дата | |
Msg-id | 20210106175837.be4cmj3b4ibzkipy@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help) (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help)
Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help) Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help) |
Список | 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
В списке pgsql-hackers по дате отправления: