[MDEV-28961] Partition management with non-default alter_algorihm / old_alter_table is not possible Created: 2022-06-27 Updated: 2023-11-28 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Data Definition - Alter Table, Partitioning |
| Affects Version/s: | 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9 |
| Fix Version/s: | 10.11 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Elena Stepanova | Assignee: | Alexey Botchkov |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
In 10.3 a new system variable alter_algorithm was introduced, and previously boolean variable old_alter_table was turned into an alias of alter_algorithm. It made partition management with a non-default value of old_alter_table or alter_algorithm impossible. Any value other than the default alter_algorithm=DEFAULT old_alter_table=0 makes ALTER fail:
The confusing message does not help, as it says that COPY/INPLACE is not supported, but is thrown on any value of alter_algorithm:
And when explicit locking is involved, it also looks strange:
If there are cases when none of allowed values for locking modes and alter algorithms is supported and "default" means something other than of of the enumerated values, at least it needs to be documented (maybe it already is, I couldn't find it). |