Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-15519

CHECKSUM TABLE gives different results across MariaDB 10.0 and 10.2

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Confirmed (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.0, 10.2
    • Fix Version/s: 10.3, 10.4
    • Component/s: Server
    • Labels:
      None
    • Environment:
      GNU/Linux

      Description

      According to https://mariadb.com/kb/en/library/checksum-table/ only older MySQL servers would yield different results.

      As it turns out, supported, widely used and deployed MariaDB instances will also return different results for the exact same table structure and data?!

      Comparing 10.0 (Ubuntu LTS repo release) and 10.2 (MariaDB official stable repo release).

      CHECKSUM TABLE badcs;
      

      MariaDB 10.0: 1873571331
      MariaDB 10.2: 3472699532

      Even worse, MySQL is different on it's own:
      MySQL 5.6.34: 260370412

      But I'm interested here in MariaDB only.
      It seems that MyISAM tables will produce same results across each server version/flavour, so all OK as expected with checksumming process done on exact same table/data.

      Only InnoDB will (mis)behave like this, thus effectively breaking entire point of CHECKSUM-ming data across servers.

      Isn't this suppose to be standard's compliant command?

      In attachment there's my sample table with few rows. So it's easy to be reproduced.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              serg Sergei Golubchik
              Reporter:
              stamster Nemanja Stambolic
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:

                  Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.