MySQL Bugs: #9617: Setting max_heap_table_size seems to not work correctly

Bug #9617	Setting max_heap_table_size seems to not work correctly
Submitted:	4 Apr 2005 17:07	Modified:	9 May 2005 12:11
Reporter:	James Mangold	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.1.9	OS:	Linux (linux redhat)
Assigned to:		CPU Architecture:	Any

Description:
I am trying to set max heap table size to 6000000000 (6gb)  on a box that has 6gb of memory. It seems to be seeting it to a different number, and I am not sure how it gets it. The new value is: 4230196224. I have tried different combinations > 3gb and they all get different numbers. Help!!!!!!!!

How to repeat:
issue set max_heap_table_size=30000000000; and see what happens. Try other values as well

Suggested fix:
overflow??? some calculation going on after variable is set??

this is a 32bit system i assume? on 32bit system no single process can allocate more than 4GB total ...

Yes - we just figured that 4gb limit out. Thanks for tour Response! We will be lookinh at putting our Indexes on a RAMDisk and leaving the data on a RAID 0 array.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".