Am 08.12.22 um 23:55 schrieb Gordan Bobic:
On Fri, Dec 9, 2022 at 12:31 AM Reindl Harald <h.reindl@thelounge.net> wrote:
2.2) Database doesn't crash because the damage merely corrupts a single value but the record structure remains sound.
So it is that 2.2) point where the InnoDB checksum gives you anything
moron it don't matter if you find it useful - the whole point was that you pretended the filesystem can do the same with it's checksums which is nonsense
You are conveniently ignoring the fact that in the vast majority of cases what InnoDB checksums will catch is silent disk corruption rather than database internals corruption.
i ignore nothing but filesystem corruption is still a different topic
So the one narrow edge case you are clinging to as the full justification of your abusive behaviour and delusions of grandeur are a tiny fraction of a percent of the errors that will cause InnoDB checksums to fail - and outside that narrow edge case all of the rest of them will be caught and handled better at layers below the database itself.
the topic was and still is "Some of us run MariaDB on file systems that do their own block checksumming, and thus run innodb_checksum_algorithm=none" where you mix two completly independent layers
So either you are arguing in bad faith, or you really are extensively ignorant of typical failure patterns.
the topic was and still is "Some of us run MariaDB on file systems that do their own block checksumming, and thus run innodb_checksum_algorithm=none" where you mix two completly independent layers