Bug #60637 | InnoDB option to have a file per database | ||
---|---|---|---|
Submitted: | 25 Mar 2011 13:14 | Modified: | 25 Mar 2011 14:02 |
Reporter: | Victor Ferrada | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S4 (Feature request) |
Version: | 5.5.9 | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | innodb_file_per_database, innodb_file_per_table |
[25 Mar 2011 13:14]
Victor Ferrada
[25 Mar 2011 14:02]
Valeriy Kravchuk
This feature may be useful in some cases.
[14 Nov 2012 10:04]
Rolf Neuberger
Seconding the request. This is a good middle ground between default behaviour and the existing file-per-table option. Usually tables within a database are the highest-priority candidates for joins, so keeping them together in one file provides useful semantics to the OS, to help with caching and allocation strategies based on natural data locality. Nice little (side) benefits: *Reduction in the sheer amount of open files vs file-per-table *Reduced inode usage *simplified maintenance
[25 Apr 2013 7:23]
Juanjo Garcia
I also ask for this feature. Having one file (with extents) per database is worth because of ease of management, ability to shrink, and to define data size of databases. And I think that having the logic to create a file per table, implementing the file creation at "create database" command will not be difficult to implement.
[15 Apr 2016 20:26]
Bill Karwin
FWIW, MySQL 5.7 now has an option to create general tablespaces with a separate .ibd datafile per tablespace. When you create or alter an InnoDB table, you can declare the tablespace in which to create the table. See: http://mysqlserverteam.com/general-tablespaces-in-mysql-5-7-details-and-tips/ https://dev.mysql.com/doc/refman/5.7/en/create-tablespace.html Does this resolve the need for this feature request?