Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
As discussed in MDEV-17484, the value for eq_range_index_dive_limit needs to be raised to 200.
Attachments
Issue Links
- relates to
-
MDEV-15253 Default optimizer setting changes for MariaDB 10.4
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Fix Version/s | 10.4 [ 22408 ] |
Description |
As discussed in [ |
Description |
As discussed in [ |
As discussed in [|https://jira.mariadb.org/browse/MDEV-17484], the value for eq_range_index_dive needs to be raised to 200.
|
Description |
As discussed in [|https://jira.mariadb.org/browse/MDEV-17484], the value for eq_range_index_dive needs to be raised to 200.
|
As discussed in [ |
Summary | New defaults for eq_range_index_dive_limit in 10.4 | New defaults for eq_range_index_dive_limit |
Assignee | Varun Gupta [ varun ] |
Link |
This issue relates to |
Fix Version/s | 10.4.3 [ 23230 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 92456 ] | MariaDB v4 [ 133858 ] |
Hi varun,
Please add --echo # comments before the ANALYZE statements in the testcase. The comments should explain what exactly the test is expecting to see in the ANALYZE output (type=range, rows about ... this many values, because ... ).
Ok to push after this is addressed.