mariadb/storage/myisammrg
Mattias Jonsson e0887df8e1 Bug#11766249 bug#59316: PARTITIONING AND INDEX_MERGE MEMORY LEAK
When executing row-ordered-retrieval index merge,
the handler was cloned, but it used the wrong
memory root, so instead of allocating memory
on the thread/query's mem_root, it used the table's
mem_root, resulting in non released memory in the
table object, and was not freed until the table was
closed.

Solution was to ensure that memory used during cloning
of a handler was allocated from the correct memory root.

This was implemented by fixing handler::clone() to also
take a name argument, so it can be used with partitioning.
And in ha_partition only allocate the ha_partition's ref, and
call the original ha_partition partitions clone() and set at cloned
partitions.

Fix of .bzrignore on Windows with VS 2010
2011-03-25 12:36:02 +01:00
..
.cvsignore
CMakeLists.txt
ha_myisammrg.cc Bug#11766249 bug#59316: PARTITIONING AND INDEX_MERGE MEMORY LEAK 2011-03-25 12:36:02 +01:00
ha_myisammrg.h Bug#11766249 bug#59316: PARTITIONING AND INDEX_MERGE MEMORY LEAK 2011-03-25 12:36:02 +01:00
make-ccc
Makefile.am
myrg_close.c
myrg_create.c
myrg_def.h
myrg_delete.c
myrg_extra.c
myrg_info.c
myrg_locking.c
myrg_open.c
myrg_panic.c
myrg_queue.c
myrg_range.c
myrg_records.c
myrg_rfirst.c
myrg_rkey.c
myrg_rlast.c
myrg_rnext.c
myrg_rnext_same.c
myrg_rprev.c
myrg_rrnd.c
myrg_rsame.c
myrg_static.c
myrg_update.c
myrg_write.c
plug.in