[MDEV-25066] IMPORT TABLESPACE not possible if source table had column moved in INSTANT mode Created: 2021-03-05 Updated: 2021-12-15 Resolved: 2021-10-31 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.4.18, 10.5.9 |
| Fix Version/s: | 10.4.22, 10.5.13, 10.6.5 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Hartmut Holzgraefe | Assignee: | Eugene Kosov (Inactive) |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Assume that we have created a table with a certain column order:
but later decide to change that order, and take advantage of this being possible as an instant operation in MariaDB 10.4 and later:
Now lets assume we want to create a copy of this table, and use tablespace import for that. Let's start by create the new copy as a copy of the old table schema, and name it t2:
Now to get the data over, too, lets start by discarding the new tables tablespace right away:
and flush the original table for export:
Then copy over the .ibd and .cfg files:
then unlock t1 and try to import the data into t2:
This should succeed, as both tables look the same on the SQL level, but fails with:
|