Bug #33372 | InnoDB free: 0 on a newly created ( and non 0 size) table | ||
---|---|---|---|
Submitted: | 19 Dec 2007 16:45 | Modified: | 8 Jan 2008 20:24 |
Reporter: | Matthew Lord | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.0.52 | OS: | Any |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
Tags: | free space, innodb, tablespace size |
[19 Dec 2007 16:45]
Matthew Lord
[20 Dec 2007 12:38]
Heikki Tuuri
Matt, Paul, InnoDB free means the number of 1 MB totally free extents minus a safety margin. It is kind of 'guaranteed' free space. For a very small table, the .ibd file is < 1 MB, which means InnoDB free will show 0. Even if InnoDB free shows 0, you can insert rows, as long as you do not need to allocate new extents. Paul, can you add this explanation to the manual, to the appropriate place? Vasil a few weeks ago in 5.1 moved the 'InnoDB free' from the table comment to an Information Schema table (deleted_length or something like that in MySQL talk). Regards, Heikki
[20 Dec 2007 16:14]
Paul DuBois
Changing to Server: Documentation/Verified because this is a documentation issue. Assigning to myself.
[8 Jan 2008 20:24]
Paul DuBois
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products. Clarified the SHOW TABLE STATUS page using Heikki's explanation.