Details
Critical Description
See details in the attached test case. If we create the right spread of values in the key and pick the range just right, when rowid_filter optimizer switch is enabled, the optimizer will sacrifice a part of the key for the rowid_filter. As a result we use only the u_delete_user and end up examining 5K+ rows out of 10K in the table. If we disable rowid_filter, the user_name constraint is being used, and we examine only 1 row.
Attachments
Issue Links
- causes
-
MDEV-30142 rowid_filter: negative access cost factor values
-
- Closed
-
- is caused by
-
MDEV-16188 Use in-memory PK filters built from range index scans
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-