[MDEV-29815] An absurd execution plan for a query in rowid_filter_innodb.test Created: 2022-10-18  Updated: 2023-12-05

Status: Stalled
Project: MariaDB Server
Component/s: Optimizer
Affects Version/s: 10.5
Fix Version/s: 10.4

Type: Bug Priority: Major
Reporter: Igor Babaev Assignee: Igor Babaev
Resolution: Unresolved Votes: 0
Labels: None


 Description   

The outpu of the EXPLAIN command for the query

( select * from t1
 
where (f1 is null and f2 is null) and (f2 between 'a' and 'z' or f1 in ('a')))
 
union
 
( select * from t1
 
where (f1 is null and f2 is null) and (f2 between 'a' and 'z' or f1 in ('a')));

contains the line:

1	PRIMARY	t1	ref|filter	f1,f2	f1|f1	13|13	const	1 (2%)  Using index condition; Using where; Using rowid filtter

.
It means that a range rowid filter fir index on f1 is used for ref access by the same index. Expected either ref f1, or ref|filter f1|f2, or ref|filter f2|f1.

 Comments   
Comment by Julien Fritsch [ 2023-12-05 ]

Automated message:
----------------------------
Since this issue has not been updated since 6 weeks, it's time to move it back to Stalled.

Comment by JiraAutomate [ 2023-12-05 ]

Automated message:
----------------------------
Since this issue has not been updated since 6 weeks, it's time to move it back to Stalled.

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