Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.2(EOL), 10.3(EOL)
Description
Because of corruption bugs (MDEV-13795, MDEV-14332), we had to refuse LOCK=NONE table-rebuilding ALTER when indexed virtual columns exist.
It is technically possible to evaluate indexed virtual column values in row_log_table_apply() if we use the altered_table there. We should do that and lift the restriction.
Attachments
Issue Links
- duplicates
-
MDEV-25865 Lockless schema updates, Alter table LOCK=NONE
- Closed
- is caused by
-
MDEV-13795 ALTER TABLE…DROP PRIMARY KEY, ADD PRIMARY KEY fails when VIRTUAL columns exist
- Closed
-
MDEV-14332 Corruption during online table-rebuilding ALTER when VIRTUAL columns exist, causes assertion failure
- Closed
- relates to
-
MDEV-17468 Avoid table rebuild on operations on generated columns
- Stalled
-
MDEV-17598 InnoDB index option for per-record transaction ID
- Open
-
MDEV-14046 Allow ALGORITHM=INPLACE for 10.1 tables that contain virtual columns
- Closed
-
MDEV-15476 Inplace algorithm doesn't support changing virtual column datatype
- Stalled
-
MDEV-16332 Allow ALGORITHM=NOCOPY or INSTANT for changes of virtual column type
- Confirmed
-
MDEV-17035 Support ALGORITHM=NOCOPY for CHANGE virtual column expression
- Open
-
MDEV-19214 Virtual column type cannot be converted from one to another - unhelpful error message
- Open
-
MDEV-32668 tables with UNIQUE blob columns cannot be alter_algorithm=INSTANT modified
- Open