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

ALTER TABLE ALGORITHM=NOCOPY does not work after upgrade

    XMLWordPrintable

    Details

      Description

      Here is the repro step.

      1) install 10.1.4 using binary tarballs.
      2) create table

      CREATE TABLE `pet4` ( `build_time` double(18,7) DEFAULT NULL, KEY `idx1` (`build_time`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 row_format=compact;
      

      3) upgrade the instance with 10.4.25. This can be done by yum/rpm install.
      4) run alter against table created in #2.

      MariaDB [test]> ALTER TABLE pet4 ADD `i1` INTEGER, algorithm=nocopy, lock=none;
      ERROR 1845 (0A000): ALGORITHM=NOCOPY is not supported for this operation. Try ALGORITHM=INPLACE
      

      #4 works without error, when create is created with v10.4.25.

      MariaDB [test]> CREATE TABLE `pet5` (
          ->   `build_time` double(18,7) DEFAULT NULL,
          ->   KEY `idx1` (`build_time`)
          -> ) ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=COMPACT;
      Query OK, 0 rows affected (0.009 sec)
       
      MariaDB [test]> ALTER TABLE pet5 ADD `i1` INTEGER, algorithm=nocopy, lock=none;
      Query OK, 0 rows affected (0.004 sec)
      Records: 0  Duplicates: 0  Warnings: 0
      

        Attachments

        1. 10.1.48.tar.gz
          656 kB
        2. 10.4.25-after-alter.tar.gz
          333 kB
        3. 10.4.25-before-alter.tar.gz
          330 kB
        4. CS0404325.tar.gz
          664 kB

          Issue Links

            Activity

              People

              Assignee:
              midenok Aleksey Midenkov
              Reporter:
              allen.lee@mariadb.com Allen Lee
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration

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