Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help)
От | Bruce Momjian |
---|---|
Тема | Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help) |
Дата | |
Msg-id | 20210106170808.GF32172@momjian.us обсуждение исходный текст |
Ответ на | Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help) (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: data_checksums enabled by default (was: Move --data-checksums to common options in initdb --help)
|
Список | pgsql-hackers |
On Wed, Jan 6, 2021 at 12:02:40PM -0500, Stephen Frost wrote: > > It unfortunately also hurts other workloads. If we moved towards a saner > > compression algorithm that'd perhaps not be an issue anymore... > > I agree that improving compression performance would be good but I don't > see that as relevant to the question of what our defaults should be. > > imv, enabling page checksums is akin to having fsync enabled by default. > Does it impact performance? Yes, surely quite a lot, but it's also the > safe and sane choice when it comes to defaults. Well, you know fsyncs are required to recover from an OS crash, which is more likely than detecting data corruption. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee
В списке pgsql-hackers по дате отправления: