[MDEV-20073] ALGORITHM=INSTANT fails while adding new column Created: 2019-07-16 Updated: 2021-11-26 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.4.6 |
| Fix Version/s: | 10.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | Maikel Punie | Assignee: | Marko Mäkelä |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | innodb | ||
| Description |
|
when trying to add a column to a big innodb table we get an error saying the column type can not be changed with ALGORITHM=INSTANT, but we are trying to add a column.
|
| Comments |
| Comment by Maikel Punie [ 2019-07-29 ] | ||
|
Any update on this one? | ||
| Comment by Yitzchak [ 2021-07-08 ] | ||
|
I am also having this happen, in an amazon rds instance with version 10.4.18. It would be nice to know if there's something about the particular table or replication or something that causes this behavior? After doing (in a restored snapshot) `alter table tablename force;`, I can add columns without locking. Is there anything I can do to make it work in my main db? | ||
| Comment by Yitzchak [ 2021-07-08 ] | ||
|
This seems to be a problem with (some, but not all, and I would love to know what the underlying problem is) tables built (or last fully altered) under an earlier version of mariadb/innodb. {{MariaDB [shiftboard_com_2]> alter online table coverage_snapshot add publish_date_utc datetime; MariaDB [shiftboard_com_2]> alter online table coverage_snapshot add publish_date_utc datetime; MariaDB [shiftboard_com_2]> select version();
---------------------
--------------------- If that is correct, is there a way to determine which tables will have this problem? |