mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 03:52:35 +01:00
a8bd6a9813
When QUICK_GROUP_MIN_MAX_SELECT is initialized or being reset it stores the prefix of the last group of the index chosen for retrieving data (last_value). Later, when looping through records at get_next() method, the server checks whether the retrieved group is the last, and if so, it finishes processing. At the same time, it looks like there is no need for that additional check since method next_prefix() returns HA_ERR_KEY_NOT_FOUND or HA_ERR_END_OF_FILE when there are no more satisfying records. If we do not perform the check, we do not need to retrieve and store last_value either. This commit removes using of last_value from QUICK_GROUP_MIN_MAX_SELECT. Reviewer: Sergei Petrunia <sergey@mariadb.com>
20 lines
445 B
Text
20 lines
445 B
Text
--- ./main/innodb_ext_key.result
|
|
+++ ./main/innodb_ext_key.reject
|
|
@@ -244,7 +244,7 @@
|
|
Variable_name Value
|
|
Handler_read_first 0
|
|
Handler_read_key 21
|
|
-Handler_read_last 1
|
|
+Handler_read_last 0
|
|
Handler_read_next 0
|
|
Handler_read_prev 0
|
|
Handler_read_retry 0
|
|
@@ -266,7 +266,7 @@
|
|
Variable_name Value
|
|
Handler_read_first 0
|
|
Handler_read_key 6
|
|
-Handler_read_last 1
|
|
+Handler_read_last 0
|
|
Handler_read_next 0
|
|
Handler_read_prev 0
|
|
Handler_read_retry 0
|