SHOW TABLE STATUS reports unappropriate value Max_data_length

Bug #677868 reported by shinguz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
PBXT
Fix Committed
Undecided
Vladimir Kolesnikov

Bug Description

When playing around with PBXT MEMORY tables I found that Max_data_length is reported inappropriately for the SHOW TABLE STATUS command:

+-------------+--------+---------+----------------+-------------+-----------------+
| Name | Engine | Rows | Avg_row_length | Data_length | Max_data_length |
+-------------+--------+---------+----------------+-------------+-----------------+
| pbxt | PBXT | 0 | 88 | 1024 | 16777215 |
| pbxt_memory | PBXT | 1048576 | 88 | 184550400 | 16777215 |
| test | MyISAM | 1048576 | 20 | 20971520 | 281474976710655 |
+-------------+--------+---------+----------------+-------------+-----------------+

I assume this is related to the max_heap_table size which is by default 16M.

Same problem for/with PBXT DISK tables.

Related branches

Changed in pbxt:
assignee: nobody → Vladimir Kolesnikov (vkolesnikov)
status: New → In Progress
Changed in pbxt:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.