summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorKailasnath Nagarkar <kailasnath.nagarkar@oracle.com>2016-08-26 11:11:27 +0530
committerKailasnath Nagarkar <kailasnath.nagarkar@oracle.com>2016-08-26 11:11:27 +0530
commit97fad8518bdce19938fdf55cbb5858e31e9ac464 (patch)
tree6eca30c76bb6bf99133bcf31851ee8a0f9d12cc7 /scripts
parent55a2babcefc9a9f46534f8e6e4b5ca12d94c1105 (diff)
downloadmariadb-git-97fad8518bdce19938fdf55cbb5858e31e9ac464.tar.gz
Bug #23303485 : HANDLE_FATAL_SIGNAL (SIG=11) IN
SUBSELECT_UNION_ENGINE::NO_ROWS This patch is specific for mysql-5.5 ISSUE: When max_join_size is used and union query results in evaluation of tuples greater than max_join_size, the join object is not created, and is set to NULL. However, this join object is further dereferenced by union logic to determine if query resulted in any number of rows being returned. Since, the object is NULL, it results in program terminating abnormally. SOLUTION: Added check to verify if join object is created. If join object is created, it will be used to determine if query resulted in any number of rows. Else, when join object is not created, we return 'false' indicating that there were no rows for the query.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions