summaryrefslogtreecommitdiff
path: root/storage/bdb/test/rpc001.tcl
diff options
context:
space:
mode:
authorJacob Mathew <jacob.mathew@mariadb.com>2018-08-29 17:36:16 -0700
committerJacob Mathew <jacob.mathew@mariadb.com>2018-08-29 17:36:16 -0700
commit4885baf682f04eea6317cab518ada794c7b746e4 (patch)
treeefb4239b33764fa37a8e6e00612147094f3f17af /storage/bdb/test/rpc001.tcl
parente10ca66bab04960688ccc2d3a3af4fbad7c06b02 (diff)
downloadmariadb-git-bb-10.3-MDEV-16889.tar.gz
MDEV-16889: Spider Crash mysqld got exception 0xc0000005bb-10.3-MDEV-16889
The SELECT with the INNER JOIN is executed with one of the two tables being optimized as a constant table, which is pre-read. Spider nevertheless attempts to push down the join to the data node. The crash occurs because the constant table is excluded from the optimized query that Spider attempts to push down. In order for Spider to be able to push down a join, the following conditions need to be met: - All of the tables involved in the join need to be included in the optimized query that Spider pushes down. When any of the tables involved in the join is a constant table, it is excluded from the optimized query that Spider attempts to push down. - All fields involved in the query need to be members of tables included in the optimized query. I fixed the problem by preventing Spider from pushing down queries that include a field that is not a member of a table included in the optimized query. This solution fixes the reported problem and also fixes other potential problems. Author: Jacob Mathew. Reviewer: Kentoku Shiba.
Diffstat (limited to 'storage/bdb/test/rpc001.tcl')
0 files changed, 0 insertions, 0 deletions