Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.4.0-1
Description
The current default settings are:
optimizer_use_condition_selectivity=1
|
use_stat_tables=NEVER
|
This means many optimizations are not enabled.
During discussion on the optimizer call, figured that we should use defaults like so:
optimizer_use_condition_selectivity=4
|
use_stat_tables=PREFERABLY
|
The task is:
- change the defaults
- This will cause some MTR test result differences
- Go through the failing test and see:
- some tests specifically require old settings. Set the variables for these tests.
- some tests dont' update test results for these.
cc igor, cvicentiu, sanja, varun_raiko, shagalla
Attachments
Issue Links
- duplicates
-
MDEV-9999 Change the default value of optimizer_use_condition_selectivity
-
- Closed
-
- includes
-
MDEV-16374 filtered shows 0 for materilization scan for a semi join, which makes optimizer always pick materialization scan over materialization lookup
-
- Closed
-
-
MDEV-16695 Estimate for rows of derived tables is very high when we are using index_merge union
-
- Closed
-
-
MDEV-16921 Filtered shows 0 with derived tables/views when optimizer_use_condition_selectivity is set to 3
-
- Closed
-
-
MDEV-16995 ER_CANT_CREATE_GEOMETRY_OBJECT encountered for a query with optimizer_use_condition_selectivity>=3
-
- Closed
-
-
MDEV-17023 Crash during read_histogram_for_table with optimizer_use_condition_selectivity set to 4
-
- Closed
-
-
MDEV-17032 Estimates are higher for partitions of a table with @@use_stat_tables= PREFERABLY
-
- Closed
-
-
MDEV-17039 Query plan changes when we use GROUP BY optimization with optimizer_use_condition_selectivity=4 and use_stat_tables= PREFERABLY
-
- Closed
-
-
MDEV-17255 New optimizer defaults and ANALYZE TABLE
-
- Closed
-
-
MDEV-17297 stats.records=0 for a table of Archive engine when it has rows, when we run ANALYZE command
-
- Closed
-
-
MDEV-17752 Plan changes from hash_index_merge to index_merge with new optimizer defaults
-
- Closed
-
-
MDEV-17778 Alter table leads to a truncation warning with ANALYZE command
-
- Closed
-
-
MDEV-17784 Analyze table returns warnings due to rounding error or overflow while collection of EITS
-
- Stalled
-
- is blocked by
-
MDEV-16307 Incorrect results when using BNLH join instead of BNL join with views
-
- Closed
-
- relates to
-
MDEV-13628 ORed condition in pushed index condition is not removed from the WHERE
-
- Closed
-
-
MDEV-13905 condition in pushed index condition is not removed from the WHERE in BNL joins
-
- Stalled
-
-
MDEV-15321 different results when using value of optimizer_use_condition_selectivity=4 and =1
-
- Closed
-
-
MDEV-17734 AddressSanitizer: use-after-poison in create_key_parts_for_pseudo_indexes
-
- Closed
-
-
MDEV-22537 optimizer_use_cond_selectivity > 1 can cause slow plans
-
- Closed
-
-
MDEV-15306 Wrong/Unexpected result with the value optimizer_use_condition_selectivity set to 4
-
- Closed
-
-
MDEV-15368 Unnecessary condition used in Index Condition Pushdown
-
- Stalled
-
-
MDEV-17903 New optimizer defaults: change optimize_join_buffer_size to be ON
-
- Closed
-
-
MDEV-18355 Switching the results for plans when there was query plan change with the new optimizer defaults
-
- Stalled
-
-
MDEV-18551 New defaults for eq_range_index_dive_limit
-
- Closed
-
-
MDEV-18608 Defaults for 10.4: histogram size should be set
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Description |
The current default settings are:
{noformat} optimizer_use_condition_selectivity=1 join_cache_level=2 use_stat_tables=NEVER {noformat} This means many optimizations are not enabled. During discussion on the optimizer call, figured that we should use defaults like so: {noformat} join_cache_level=3 (or even 4) optimizer_use_condition_selectivity=4 use_stat_tables=PREFERABLY {noformat} |
The current default settings are:
{noformat} optimizer_use_condition_selectivity=1 join_cache_level=2 use_stat_tables=NEVER {noformat} This means many optimizations are not enabled. During discussion on the optimizer call, figured that we should use defaults like so: {noformat} join_cache_level=4 optimizer_use_condition_selectivity=4 use_stat_tables=PREFERABLY {noformat} |
Description |
The current default settings are:
{noformat} optimizer_use_condition_selectivity=1 join_cache_level=2 use_stat_tables=NEVER {noformat} This means many optimizations are not enabled. During discussion on the optimizer call, figured that we should use defaults like so: {noformat} join_cache_level=4 optimizer_use_condition_selectivity=4 use_stat_tables=PREFERABLY {noformat} |
The current default settings are:
{noformat} optimizer_use_condition_selectivity=1 join_cache_level=2 use_stat_tables=NEVER {noformat} This means many optimizations are not enabled. During discussion on the optimizer call, figured that we should use defaults like so: {noformat} join_cache_level=4 optimizer_use_condition_selectivity=4 use_stat_tables=PREFERABLY {noformat} The task is: - change the defaults - This will cause some MTR test result differences - Go through the failing test and see: -- some tests specifically require old settings. Set the variables for these tests. -- some tests dont' update test results for these. |
Description |
The current default settings are:
{noformat} optimizer_use_condition_selectivity=1 join_cache_level=2 use_stat_tables=NEVER {noformat} This means many optimizations are not enabled. During discussion on the optimizer call, figured that we should use defaults like so: {noformat} join_cache_level=4 optimizer_use_condition_selectivity=4 use_stat_tables=PREFERABLY {noformat} The task is: - change the defaults - This will cause some MTR test result differences - Go through the failing test and see: -- some tests specifically require old settings. Set the variables for these tests. -- some tests dont' update test results for these. |
The current default settings are:
{noformat} optimizer_use_condition_selectivity=1 join_cache_level=2 use_stat_tables=NEVER {noformat} This means many optimizations are not enabled. During discussion on the optimizer call, figured that we should use defaults like so: {noformat} join_cache_level=4 optimizer_use_condition_selectivity=4 use_stat_tables=PREFERABLY {noformat} The task is: - change the defaults - This will cause some MTR test result differences - Go through the failing test and see: -- some tests specifically require old settings. Set the variables for these tests. -- some tests dont' update test results for these. cc [~igor] [~cvicentiu] [[~sanja] [~varun_raiko][~shagalla] |
Assignee | Varun Gupta [ varun ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Sprint | 10.3.5-1 [ 229 ] |
Priority | Major [ 3 ] | Blocker [ 1 ] |
Link |
This issue relates to |
Link | This issue relates to MDEV-15314 [ MDEV-15314 ] |
Link |
This issue relates to |
Link | This issue relates to MDEV-13905 [ MDEV-13905 ] |
Link |
This issue relates to |
Link | This issue relates to MDEV-15368 [ MDEV-15368 ] |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.3 [ 22126 ] |
Priority | Blocker [ 1 ] | Critical [ 2 ] |
Sprint | 10.3.5-1 [ 229 ] |
Summary | Default optimizer setting changes for MariaDB 10.3 | Default optimizer setting changes for MariaDB 10.4 |
Link |
This issue is blocked by |
Sprint | 10.4.0-1 [ 254 ] |
Rank | Ranked lower |
Link | This issue is blocked by MDEV-16337 [ MDEV-16337 ] |
Description |
The current default settings are:
{noformat} optimizer_use_condition_selectivity=1 join_cache_level=2 use_stat_tables=NEVER {noformat} This means many optimizations are not enabled. During discussion on the optimizer call, figured that we should use defaults like so: {noformat} join_cache_level=4 optimizer_use_condition_selectivity=4 use_stat_tables=PREFERABLY {noformat} The task is: - change the defaults - This will cause some MTR test result differences - Go through the failing test and see: -- some tests specifically require old settings. Set the variables for these tests. -- some tests dont' update test results for these. cc [~igor] [~cvicentiu] [[~sanja] [~varun_raiko][~shagalla] |
The current default settings are:
{noformat} optimizer_use_condition_selectivity=1 use_stat_tables=NEVER {noformat} This means many optimizations are not enabled. During discussion on the optimizer call, figured that we should use defaults like so: {noformat} optimizer_use_condition_selectivity=4 use_stat_tables=PREFERABLY {noformat} The task is: - change the defaults - This will cause some MTR test result differences - Go through the failing test and see: -- some tests specifically require old settings. Set the variables for these tests. -- some tests dont' update test results for these. cc [~igor] [~cvicentiu] [[~sanja] [~varun_raiko][~shagalla] |
Link |
This issue includes |
Link | This issue is blocked by MDEV-16337 [ MDEV-16337 ] |
Link | This issue relates to MDEV-16607 [ MDEV-16607 ] |
Link |
This issue is duplicated by |
Link |
This issue includes |
Link |
This issue is duplicated by |
Link |
This issue includes |
Link |
This issue includes |
Epic Link | PT-76 [ 68557 ] |
Link |
This issue includes |
Link |
This issue includes |
Link |
This issue includes |
Link |
This issue includes |
Link |
This issue includes |
Link | This issue relates to MDEV-15314 [ MDEV-15314 ] |
Rank | Ranked higher |
Link |
This issue relates to |
Link |
This issue includes |
Link | This issue includes MDEV-17784 [ MDEV-17784 ] |
Labels | defaults |
Link | This issue relates to MDEV-16607 [ MDEV-16607 ] |
Link |
This issue relates to |
Link |
This issue relates to |
Link |
This issue relates to |
Link |
This issue relates to |
Link |
This issue relates to |
Link |
This issue includes |
Fix Version/s | 10.4.1 [ 23228 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Description |
The current default settings are:
{noformat} optimizer_use_condition_selectivity=1 use_stat_tables=NEVER {noformat} This means many optimizations are not enabled. During discussion on the optimizer call, figured that we should use defaults like so: {noformat} optimizer_use_condition_selectivity=4 use_stat_tables=PREFERABLY {noformat} The task is: - change the defaults - This will cause some MTR test result differences - Go through the failing test and see: -- some tests specifically require old settings. Set the variables for these tests. -- some tests dont' update test results for these. cc [~igor] [~cvicentiu] [[~sanja] [~varun_raiko][~shagalla] |
The current default settings are:
{noformat} optimizer_use_condition_selectivity=1 use_stat_tables=NEVER {noformat} This means many optimizations are not enabled. During discussion on the optimizer call, figured that we should use defaults like so: {noformat} optimizer_use_condition_selectivity=4 use_stat_tables=PREFERABLY {noformat} The task is: - change the defaults - This will cause some MTR test result differences - Go through the failing test and see: -- some tests specifically require old settings. Set the variables for these tests. -- some tests dont' update test results for these. cc [~igor], [~cvicentiu], [~sanja], [~varun_raiko], [~shagalla] |
Link | This issue relates to MDEV-18355 [ MDEV-18355 ] |
Link |
This issue relates to |
Link |
This issue relates to |
Rank | Ranked lower |
Rank | Ranked higher |
Remote Link | This issue links to "Page (MariaDB Confluence)" [ 31355 ] |
Workflow | MariaDB v3 [ 85497 ] | MariaDB v4 [ 133470 ] |
Link |
This issue relates to |
Remote Link | This issue links to "Page (MariaDB Confluence)" [ 35215 ] |