Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
None
Description
MariaDB Server's grammar supports the CREATE TABLESPACE, ALTER TABLESPACE, and DROP TABLESPACE statements. These statements seem to have been inherited from MySQL NDB Cluster.
MySQL 5.7 supports these statements for InnoDB as well, but we chose not to merge that support in MariaDB 10.2.
https://mariadb.com/kb/en/library/alter-tablespace/
https://mariadb.com/kb/en/library/create-tablespace/
https://mariadb.com/kb/en/library/drop-tablespace/
The MySQL-compatible statements will actually still succeed on MariaDB, but will throw a warning. e.g.:
MariaDB [db1]> CREATE TABLESPACE `ts1` ADD DATAFILE 'ts1.ibd' ENGINE=INNODB;
|
Query OK, 0 rows affected, 1 warning (0.00 sec)
|
 |
MariaDB [db1]> SHOW WARNINGS;
|
+---------+------+------------------------------------------------------------------------------------------------+
|
| Level | Code | Message |
|
+---------+------+------------------------------------------------------------------------------------------------+
|
| Warning | 1478 | Table storage engine 'InnoDB' does not support the create option 'TABLESPACE or LOGFILE GROUP' |
|
+---------+------+------------------------------------------------------------------------------------------------+
|
1 row in set (0.00 sec)
|
Is there any reason to keep these in MariaDB?
Attachments
Issue Links
- relates to
-
MDEV-19295 Remove LOGFILE-related commands
- Open
-
MDEV-6113 merge 5.7 innodb
- Closed
-
MDEV-11426 Remove InnoDB INFORMATION_SCHEMA.FILES implementation
- Closed
-
MDEV-12309 Test migration from MySQL 5.7 with named tablespaces to MariaDB 10.2
- Stalled
-
MDEV-12702 CREATE TABLESPACE in 10.2
- Closed
-
MDEV-19293 Remove information_schema.TABLESPACES
- Open