Bug #45137 unable to limit total memory consumption
Submitted: 27 May 2009 15:24 Modified: 27 Jun 2009 19:23
Reporter: tom dwyer Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server: Memory storage engine Severity:S2 (Serious)
Version:5.1.32 OS:Solaris
Assigned to: CPU Architecture:Any

[27 May 2009 15:24] tom dwyer
After updating to 5.1.32 from 5.1.30, we can no longer limit the memory consuption, with MySQL taking over 50G of memory for queries that would formerly take less than 20G.  All parameters are same, and lowering key_buffer_size does not have any impact.

How to repeat:
run queries that combine multiple large databases and watch the memory get sucked up.
[27 May 2009 19:23] Sveta Smirnova
Thank you for the report.

Please provide repeatable test case: SHOW CREATE TABLE, dump of tables or at least SHOW TABLE STATUS output and problem query.
[27 Jun 2009 23:00] Bugs System
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".