Bug #36596 innodb_file_per_table or innodb_file_per_table = 1

• Submitted: 8 May 2008 14:46
• Modified: 8 Jun 2008 14:54
• Reporter: foo bar
• Status: No Feedback
• Category: MySQL Server
• Severity: S3 (Non-critical)
• OS: Any
• CPU Architecture: Any

[8 May 2008 14:46] foo bar

Description:
in my.cnf

Should it be
innodb_file_per_table
Or:
innodb_file_per_table = 1

The docs and examples don't seem very clear about it.

How to repeat:
Read the docs.
edit my.cnf
see which config works and which doesn't.

Suggested fix:
Fix the docs or the server.

[8 May 2008 14:51] Paul Dubois

Either way works.

Example:

http://dev.mysql.com/doc/refman/5.0/en/multiple-tablespaces.html

[8 May 2008 14:54] Valeriy Kravchuk

Manual, http://dev.mysql.com/doc/refman/5.0/en/multiple-tablespaces.html, clearly says:

" You can enable multiple tablespaces by adding this line to the [mysqld] section of my.cnf:

[mysqld]
innodb_file_per_table"

and it works exactly as documented. Settinginnodb_file_per_table=1 also works. So, what is the problem?

[8 Jun 2008 23:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".