Re: Optimizer executes inperformant subquery first
Hi Martin,
Thanks for filing a bug and uploading a test case. I will take a look at it.
As you observed the trace is truncated, and it does not include the interesting part. To see the whole trace, you will need to increase the value of optimizer_trace_max_mem_size session variable. There is a column in the trace table called MISSING_BYTES_BEYOND_MAX_MEM_SIZE that will tell you how much you need. I usually set it to 1MB. That seems to be sufficient in most cases:
set optimizer_trace_max_mem_size=1024*1024;
Since the trace will be large, it is probably better to upload it to the bug report instead of posting it here.
Øystein Grøvlen,
Senior Principal Software Engineer,
MySQL Group, Oracle,
Trondheim, Norway
Subject
Views
Written By
Posted
3605
December 06, 2013 07:12AM
1437
December 07, 2013 02:30PM
1668
December 07, 2013 03:49PM
1732
December 09, 2013 09:48AM
1650
December 18, 2013 03:04AM
Re: Optimizer executes inperformant subquery first
1442
December 19, 2013 02:45AM
1390
December 20, 2013 02:24AM
1348
December 23, 2013 08:07AM
1318
December 23, 2013 01:11PM
1416
December 18, 2013 05:16AM
1465
December 18, 2013 06:49PM
1419
December 19, 2013 02:49AM