[MDEV-29997] Partition Pruning not included in optimizer tracing Created: 2022-11-10  Updated: 2023-02-03  Resolved: 2022-12-26

Status: Closed
Project: MariaDB Server
Component/s: Optimizer
Affects Version/s: 10.11
Fix Version/s: 11.0.0

Type: Bug Priority: Major
Reporter: Rex Johnston Assignee: Sergei Petrunia
Resolution: Fixed Votes: 0
Labels: optimizer_trace

Attachments: HTML File Notes     File partition_pruning.out     File partition_pruning.sql    
Issue Links:
Relates
relates to MDEV-21092 EXISTS to IN is not reflected in the ... Closed

 Description   

There is a feature called "Partition Pruning" ( entry point:
prune_partitions()) where the optimizer figures out the set of
partitions it will need to read for a given table when running the
query.

One can see its result in "partitions" column in EXPLAIN PARTITIONS or
in EXPLAIN FORMAT=JSON.

Nothing is printed in the optimizer trace about this.

 Comments   
Comment by Sergei Petrunia [ 2022-12-26 ]

The patch is in preview-11.0-preview tree.

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