diff options
author | unknown <kroki/tomash@moonlight.home> | 2007-01-09 12:24:25 +0300 |
---|---|---|
committer | unknown <kroki/tomash@moonlight.home> | 2007-01-09 12:24:25 +0300 |
commit | 2500fac48015a2f00547a402107c25b00eb49120 (patch) | |
tree | 41934cc12f3f4f1f97f07c3201f64f8e0a704f9d /COPYING | |
parent | 37a4fbabf9f8c55cf4f90530d80cfe4e439007da (diff) | |
download | mariadb-git-2500fac48015a2f00547a402107c25b00eb49120.tar.gz |
BUG#23443: user-defined variables can consume too much memory in the
server
The problem was that when memory was exhausted HEAP engine could crash
(GROUP BY uses HEAP TABLE). Alternatively, if SET was used, it could
report an error "You may only use constant expressions with SET" instead
of "Out of memory (Needed NNNNNN bytes)".
The solution is:
- pass MY_WME to (some) calls to my_malloc() to get correct message.
- fix heap_write() so that the first key is skipped during cleanup
on ENOMEM because it wasn't inserted and doesn't have to be
deleted.
No test case is provided because we can't test out-of-memory behaviour
in our current test framework.
heap/hp_block.c:
If allocation fails, write an error message.
heap/hp_write.c:
On ENOMEM, skip the first key in cleanup, as it wasn't inserted yet.
sql/item_func.cc:
Add MY_WME so that OOM error will be reported.
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions