| Bug #2719 | Heap tables status shows wrong or missing data. | ||
|---|---|---|---|
| Submitted: | 11 Feb 2004 20:38 | Modified: | 22 Feb 2004 3:44 |
| Reporter: | Peter Zaitsev (Basic Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 4.1 | OS: | Any (all) |
| Assigned to: | Victor Vagin | CPU Architecture: | Any |
[11 Feb 2004 20:38]
Peter Zaitsev
[17 Feb 2004 19:14]
MySQL Verification Team
Verified with a result a little different:
mysql> show table status\G
*************************** 1. row ***************************
Name: btree
Type: HEAP
Row_format: Fixed
Rows: 2
Avg_row_length: 5
Data_length: 129032
Max_data_length: 3994575
Index_length: 0
Data_free: 0
Auto_increment: NULL
Create_time: NULL
Update_time: NULL
Check_time: NULL
Collation: latin1_swedish_ci
Checksum: NULL
Create_options:
Comment:
1 row in set (0.00 sec)
[22 Feb 2004 3:44]
Victor Vagin
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.
If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information
about accessing the source trees is available at
http://www.mysql.com/doc/en/Installing_source_tree.html
Additional info:
We only fixed value of Index_length for BTREE index..
All the other fields contain the actual information that we can give..
To avoid misunderstanding we added special note to manual about it..
(
For MEMORY (HEAP) tables, the Data_length,
Max_data_length, and Index_length values approximate the
actual amount of allocated memory. The allocation algorithm reserves memory
in large amounts to reduce the number of allocation operations.
)
