Bug #10317 | Max_Rows option for Innodb, Myisam and Memory engines. | ||
---|---|---|---|
Submitted: | 2 May 2005 16:28 | Modified: | 11 May 2005 18:14 |
Reporter: | Disha | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S2 (Serious) |
Version: | 5.0.4.-beta-standard | OS: | Any (Any) |
Assigned to: | Paul DuBois | CPU Architecture: | Any |
[2 May 2005 16:28]
Disha
[2 May 2005 16:55]
Sergei Golubchik
MAX_ROWS is not a hard limit, but more like a hint to storage engine, to let it chose the storage optimized for the dataset size. The manual says: `MAX_ROWS' The maximum number of rows you plan to store in the table. but we can make it more clear that MAX_ROWS is not a constraint.
[3 May 2005 6:24]
Heikki Tuuri
Hi! InnoDB ignores MAX_ROWS. Regards, Heikki
[11 May 2005 18:14]
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 product(s). Additional info: I'll clarify tht MAX_ROWS = n means the table must be able to hold *at least* n rows.