[MDEV-14341] Allow LOCK=NONE in table-rebuilding ALTER when indexed virtual columns exist Created: 2017-11-09  Updated: 2023-11-03

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.2, 10.3
Fix Version/s: 10.4

Type: Bug Priority: Major
Reporter: Marko Mäkelä Assignee: Marko Mäkelä
Resolution: Unresolved Votes: 4
Labels: online-ddl, virtual_columns

Issue Links:
Duplicate
duplicates MDEV-25865 Lockless schema updates, Alter table ... Closed
Problem/Incident
is caused by MDEV-13795 ALTER TABLE…DROP PRIMARY KEY, ADD PRI... Closed
is caused by MDEV-14332 Corruption during online table-rebuil... Closed
Relates
relates to MDEV-17468 Avoid table rebuild on operations on ... Stalled
relates to MDEV-17598 InnoDB index option for per-record tr... Open
relates to MDEV-14046 Allow ALGORITHM=INPLACE for 10.1 tabl... Closed
relates to MDEV-15476 Inplace algorithm doesn't support cha... Stalled
relates to MDEV-16332 Allow ALGORITHM=NOCOPY or INSTANT for... Confirmed
relates to MDEV-17035 Support ALGORITHM=NOCOPY for CHANGE v... Open
relates to MDEV-19214 Virtual column type cannot be convert... Open
relates to MDEV-32668 tables with UNIQUE blob columns canno... Open

 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.
Generated at Thu Feb 08 08:12:48 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.