Martin Hansson 2b734bbee9 Bug#41660: Sort-index_merge for non-first join table may ...

require O(#scans) memory

When an index merge operation was restarted, it would
re-allocate the Unique object controlling the duplicate row
ID elimination. Fixed by making the Unique object a member
of QUICK_INDEX_MERGE_SELECT and thus reusing it throughout
the lifetime of this object.

2010-06-24 15:21:23 +02:00

2.8 KiB

Raw Blame History

View Raw