summaryrefslogtreecommitdiff
path: root/CREDITS
diff options
context:
space:
mode:
authorVarun Gupta <varun.gupta@mariadb.com>2020-08-24 17:22:21 +0530
committerVarun Gupta <varun.gupta@mariadb.com>2020-08-26 06:39:14 +0530
commit65f30050aafb3821ba63a3b837c98cf4d2334254 (patch)
treeabc6c93f658a4a0422596bcef4c604123523dac7 /CREDITS
parent95831888e8a89a4e141e76d51dbfc0701552c824 (diff)
downloadmariadb-git-65f30050aafb3821ba63a3b837c98cf4d2334254.tar.gz
MDEV-18335: Assertion `!error || error == 137' failed in subselect_rowid_merge_engine::init
When duplicates are removed from a table using a hash, if the record is a duplicate it is marked as deleted. The handler API check if the record is deleted and send an error flag HA_ERR_RECORD_DELETED. When we scan over the table if the thread is not killed then we skip the records marked as HA_ERR_RECORD_DELETED. The issue here is when a query is aborted by a user (this is happening when the LIMIT for ROWS EXAMINED is exceeded), the scan over the table does not skip the records for which HA_ERR_RECORD_DELETED is sent. It just returns an error flag HA_ERR_ABORTED_BY_USER. This error flag is not checked at the upper level and hence we hit the assert. If the query is aborted by the user we should just skip reading rows and return control to the upper levels of execution.
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions