[MDEV-22465] DROP COLUMN, DROP INDEX is wrongly claimed to be ALGORITHM=INSTANT Created: 2020-05-05 Updated: 2020-05-05 Resolved: 2020-05-05 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.4.1, 10.5.0 |
| Fix Version/s: | 10.4.13, 10.5.3 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | regression | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
The following SQL test case works on 10.3 but fails to return an error on 10.4:
The reason appears to be a code change that was part of
We should not return HA_ALTER_INPLACE_INSTANT if any flags in INNOBASE_ALTER_NOREBUILD (dropping or creating secondary indexes) are set, because those are not instantaneous operations. |
| Comments |
| Comment by Marko Mäkelä [ 2020-05-05 ] | |||||||||||||||||||||||||
|
The following fix seems to work:
The second part is refining |