Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
MariaDB Server's grammar supports the CREATE LOGFILE, ALTER LOGFILE, and DROP LOGFILE statements. These statements seem to have been inherited from MySQL NDB Cluster.
https://dev.mysql.com/doc/refman/5.7/en/create-logfile-group.html
https://dev.mysql.com/doc/refman/5.7/en/alter-logfile-group.html
https://dev.mysql.com/doc/refman/5.7/en/drop-logfile-group.html
https://mariadb.com/kb/en/library/create-logfile-group/
https://mariadb.com/kb/en/library/alter-logfile-group/
https://mariadb.com/kb/en/library/drop-logfile-group/
The MySQL NDB Cluster-compatible statements will actually still succeed on MariaDB, but will throw a warning. e.g.:
MariaDB [db1]> CREATE LOGFILE GROUP lg1 ADD UNDOFILE 'undo.dat' INITIAL_SIZE = 10M;
|
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
-
-
- Open
-
-
MDEV-19294 Remove TABLESPACE-related commands
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue relates to |
| Link | This issue relates to MDEV-19293 [ MDEV-19293 ] |
| Description |
MariaDB Server's grammar supports the CREATE LOGFILE, ALTER LOGFILE, and DROP LOGFILE statements. These statements seem to have been inherited from MySQL NDB Cluster.
https://dev.mysql.com/doc/refman/5.7/en/create-logfile-group.html https://dev.mysql.com/doc/refman/5.7/en/alter-logfile-group.html https://dev.mysql.com/doc/refman/5.7/en/drop-logfile-group.html The MySQL NDB Cluster-compatible statements will actually still succeed on MariaDB, but will throw a warning. e.g.: {noformat} MariaDB [db1]> CREATE LOGFILE GROUP lg1 ADD UNDOFILE 'undo.dat' INITIAL_SIZE = 10M; 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) {noformat} Is there any reason to keep these in MariaDB? |
MariaDB Server's grammar supports the CREATE LOGFILE, ALTER LOGFILE, and DROP LOGFILE statements. These statements seem to have been inherited from MySQL NDB Cluster.
https://dev.mysql.com/doc/refman/5.7/en/create-logfile-group.html https://dev.mysql.com/doc/refman/5.7/en/alter-logfile-group.html https://dev.mysql.com/doc/refman/5.7/en/drop-logfile-group.html https://mariadb.com/kb/en/library/create-logfile-group/ https://mariadb.com/kb/en/library/alter-logfile-group/ https://mariadb.com/kb/en/library/drop-logfile-group/ The MySQL NDB Cluster-compatible statements will actually still succeed on MariaDB, but will throw a warning. e.g.: {noformat} MariaDB [db1]> CREATE LOGFILE GROUP lg1 ADD UNDOFILE 'undo.dat' INITIAL_SIZE = 10M; 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) {noformat} Is there any reason to keep these in MariaDB? |
| Assignee | Sergei Golubchik [ serg ] | Ralf Gebhardt [ ralf.gebhardt@mariadb.com ] |
| Fix Version/s | 10.4 [ 22408 ] |
| Workflow | MariaDB v3 [ 96248 ] | MariaDB v4 [ 131068 ] |
| Description |
MariaDB Server's grammar supports the CREATE LOGFILE, ALTER LOGFILE, and DROP LOGFILE statements. These statements seem to have been inherited from MySQL NDB Cluster.
https://dev.mysql.com/doc/refman/5.7/en/create-logfile-group.html https://dev.mysql.com/doc/refman/5.7/en/alter-logfile-group.html https://dev.mysql.com/doc/refman/5.7/en/drop-logfile-group.html https://mariadb.com/kb/en/library/create-logfile-group/ https://mariadb.com/kb/en/library/alter-logfile-group/ https://mariadb.com/kb/en/library/drop-logfile-group/ The MySQL NDB Cluster-compatible statements will actually still succeed on MariaDB, but will throw a warning. e.g.: {noformat} MariaDB [db1]> CREATE LOGFILE GROUP lg1 ADD UNDOFILE 'undo.dat' INITIAL_SIZE = 10M; 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) {noformat} Is there any reason to keep these in MariaDB? |
MariaDB Server's grammar supports the CREATE LOGFILE, ALTER LOGFILE, and DROP LOGFILE statements. These statements seem to have been inherited from MySQL NDB Cluster. https://dev.mysql.com/doc/refman/5.7/en/create-logfile-group.html https://dev.mysql.com/doc/refman/5.7/en/alter-logfile-group.html https://dev.mysql.com/doc/refman/5.7/en/drop-logfile-group.html https://mariadb.com/kb/en/library/create-logfile-group/ https://mariadb.com/kb/en/library/alter-logfile-group/ https://mariadb.com/kb/en/library/drop-logfile-group/ The MySQL NDB Cluster\-compatible statements will actually still succeed on MariaDB, but will throw a warning. e.g.: {noformat} MariaDB [db1]> CREATE LOGFILE GROUP lg1 ADD UNDOFILE 'undo.dat' INITIAL_SIZE = 10M; 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) {noformat} Is there any reason to keep these in MariaDB? |
| Labels | synchronization |
| Labels | synchronization |
| Issue Type | Task [ 3 ] | New Feature [ 2 ] |
| Assignee | Ralf Gebhardt [ ralf.gebhardt@mariadb.com ] |