Bug #33170 New CREATE TABLESPACE behavoir with Falcon
Submitted: 12 Dec 2007 15:45 Modified: 30 Jul 2008 13:14
Reporter: Philip Stoev Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:6.0.5 OS:Any
Assigned to: MC Brown CPU Architecture:Any

[12 Dec 2007 15:45] Philip Stoev

states that the format for CREATE TABLESPACE is

    ADD DATAFILE 'file'
    USE LOGFILE GROUP logfile_group
implying that USE LOGFILE GROUP is a mandatory field. Also, the text says:

"A log file group of one or more UNDO log files must be assigned to the tablespace to be created with the USE LOGFILE GROUP clause"

however this does not appear to match the behavior of Falcon, which does not require a USE LOGFILE GROUP clause.

How to repeat:
Server version: 6.0.5-alpha-debug-log Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> create tablespace t1 add datafile 't1' engine=falcon;
Query OK, 0 rows affected (0.03 sec)

Suggested fix:
If indeed a logfile group is optional for Falcon, it would be nice for the user to know that, in case they started reading the documentation from CREATE TABLESPACE rather than from "12.6.3 Creating the Falcon Tablespace"
[12 Dec 2007 17:13] Valeriy Kravchuk
Thank you for a documentation request. Verified just as described.
[30 Jul 2008 13:14] MC Brown
The documentation has been updated so that the USE LOGFILE GROUP is no longer a required clause of the entire CREATE TABLESPACE statement.