Details
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
-
- duplicates
-
MDEV-19720 Server crash in st_join_table::save_explain_data or Assertion `sel->quick' failed in JOIN::make_range_rowid_filters with rowid_filter=on
-
- Closed
-
- is caused by
-
MDEV-16188 Use in-memory PK filters built from range index scans
-
- Closed
-
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Activity
Transition | Time In Source Status | Execution Times |
---|
|
75d 14h 58m | 1 |
|
21h 52m | 1 |
|
6d 14h 59m | 2 |
|
17d 18h 27m | 2 |
|
1d 22h 5m | 1 |
|
1d 2h 24m | 1 |
|
14s | 1 |
|
21d 9h 58m | 1 |
|
7d 14h 23m | 1 |
|
1d 9h 33m | 1 |