Re: [HACKERS] Checksums by default?
От | Ants Aasma |
---|---|
Тема | Re: [HACKERS] Checksums by default? |
Дата | |
Msg-id | CA+CSw_sqYvdo_3R0uJP1VuFHATfPs_B=7NuKaHhRS5R6nrffDA@mail.gmail.com обсуждение исходный текст |
Ответ на | [HACKERS] Checksums by default? (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: [HACKERS] Checksums by default?
Re: [HACKERS] Checksums by default? |
Список | pgsql-hackers |
On Sat, Jan 21, 2017 at 7:39 PM, Petr Jelinek <petr.jelinek@2ndquadrant.com> wrote: > So in summary "postgresql.conf options are easy to change" while "initdb > options are hard to change", I can see this argument used both for > enabling or disabling checksums by default. As I said I would be less > worried if it was easy to turn off, but we are not there afaik. And even > then I'd still want benchmark first. Adding support for disabling checksums is almost trivial as it only requires flipping a value in the control file. And I have somewhere sitting around a similarly simple tool for turning on checksums while the database is offline. FWIW, based on customers and fellow conference goers I have talked to most would gladly take the performance hit, but not the downtime to turn it on on an existing database. Regards, Ants Aasma
В списке pgsql-hackers по дате отправления: