Details
-
Bug
-
Status: Stalled (View Workflow)
-
Critical
-
Resolution: Unresolved
-
None
Description
There is a bunch of known issues with condition selectivity computations for join prefixes : (MDEV-20740, MDEV-20595, MDEV-20697, MDEV-20740, MDEV-17783, MDEV-21633, MDEV-21813, etc)
This task is an umbrella task for fixing them.
Attachments
Issue Links
- includes
-
MDEV-33697 Improve selectivity computations for multi-part keys
-
- In Testing
-
- relates to
-
MDEV-17783 AddressSanitizer: stack-buffer-overflow in table_cond_selectivity with optimizer_use_condition_selectivity > 1, join_cache_level >2
-
- Closed
-
-
MDEV-20697 Take selectivity of join conditions into account correctly with optimizer_use_condition_selectivity > 1
-
- Stalled
-
-
MDEV-20740 Odd computations in calculate_cond_selectivity_for_table
-
- Open
-
-
MDEV-21377 Eq_ref access not picked by query with optimizer_use_condition_selectivity > 1
-
- Closed
-
-
MDEV-21633 Assertion `tmp >= 0' failed in best_access_path with rowid_filter=ON
-
- Stalled
-
-
MDEV-21813 Optimizer choosing the wrong index despite the cost calculation
-
- Stalled
-
-
MDEV-25830 optimizer_use_condition_selectivity=4 sometimes produces worse plan than optimizer_use_condition_selectivity=1
-
- Closed
-
-
MDEV-29395 Review input for 10.7-selectivity tree
-
- Closed
-
-
MDEV-29577 Rebase 10.7-selectivity tree
-
- Closed
-
- mentioned in
-
Page Loading...
Activity
Transition | Time In Source Status | Execution Times |
---|
|
327d 23h 29m | 1 |
|
785d 17h 33m | 1 |