[MDEV-30876] Back port LATERAL DERIVED coverage in optimizer trace Created: 2023-03-19  Updated: 2023-05-16  Resolved: 2023-05-15

Status: Closed
Project: MariaDB Server
Component/s: Optimizer
Fix Version/s: 11.1.1, 10.11.3, 10.4.29, 10.5.20, 10.6.13, 10.8.8, 10.9.6, 10.10.4

Type: Task Priority: Major
Reporter: Valerii Kravchuk Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MDEV-24325 Optimizer trace doesn't cover LATERAL... Closed

 Description   

MDEV-24325 added support for some details related to LATERAL DERIVED optimization into 10.6+. This request is to back port them to 10.4 and 10.5, as this optimization is enabled by default and in some cases are wrongly used. Having the details in the optimizer trace would help a lot to figure out what caused using the bad plan involving LATERAL DERIVED.

 Comments   
Comment by Sergei Petrunia [ 2023-05-15 ]

MDEV-26301 introduced changes to how the optimizer handles LATERAL DERIVED (aka Split Materialized).
Besides the fix for MDEV-26301, there was a patch pushed that improved Optimizer Trace coverage:

commit ed3e6f66a265952afded33fb134f6f8bcc31aa89
 
Author: Sergei Petrunia <sergey@mariadb.com>
 
Date:   Wed May 3 13:49:32 2023 +0300
 
 
    MDEV-26301: Split optimization refills: Optimizer Trace coverage
 
    
    Add Optimizer Trace printouts.

That commit covers what was required to be done in this MDEV.

Generated at Thu Feb 08 10:19:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.