[MDEV-32350] Can't selectively restore sequences using innodb tables from backup Created: 2023-10-04 Updated: 2023-12-18 |
|
| Status: | Confirmed |
| Project: | MariaDB Server |
| Component/s: | mariabackup, Sequences, Storage Engine - InnoDB |
| Affects Version/s: | 10.3, 10.4, 10.6, 10.5.21 |
| Fix Version/s: | 10.4, 10.5, 10.6 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Hartmut Holzgraefe | Assignee: | Michael Widenius |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
When wanting to do a selective restore of a backup taken with mariabackup DISCARD TABLESPACE / IMPORT TABLESPACE is used after preparing the backup with mariabackup --prepare --export When having a SEQUENCE backed by an InnoDB table the related .ibd tablespace file can't be discarded though:
So there does not seem to be a way to restore such a sequence from a physical backup like mariabackup. IMHO the SEQUENCE engine here should not just outright refuse such ALTER attempts, but pass them through to the underlying engine actually used for sequence storage. |
| Comments |
| Comment by Marko Mäkelä [ 2023-10-06 ] | |||||||||||||||
|
During the execution of the following, ha_innobase::discard_or_import_tablespace() is never invoked. ha_innobase::create() is.
The error code is being returned by the base member function handler::ha_discard_or_import_tablespace() and reported here:
|