[MDEV-28727] ALTER TABLE ALGORITHM=NOCOPY does not work after upgrade - Jira

XML

Word

Printable

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

causes

MDEV-29481 mariadb-upgrade prints confusing statement

is caused by

MDEV-20704 An index on a double column erroneously uses prefix compression

relates to

MDEV-16291 Allow ALGORITHM=NOCOPY for most ALTER TABLE in InnoDB

MDEV-28822 Table from older version requires table rebuild when adding column to table with multi-column index

MDEV-18827 Create utility to parse frm files and print their DDL (Full-time project - potential part-time)

MDEV-29495 Generalize can_convert_xxx() hook engine API to cover any arbitrary data type

SAMU-272 Loading...

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(2 relates to, 1 is blocked by, 17 mentioned in)

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