Details
-
Task
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-4, 10.2.4-1, 10.2.4-5, 10.0.29
Description
Poor MySQL has received some negative feedback over the years 1 2. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand.
Oracle are working on changing more defaults in 5.7 3 4 5, I think we should too.
Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf:
https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh
It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB.
- http://sql-info.de/mysql/gotchas.html
- http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/
- http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html
- http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html
- http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html
Proposed new defaults:
innodb_autoinc_lock_mode = 2 (was: 1)
|
innodb_buffer_pool_dump_at_shutdown = ON (was: OFF)
|
innodb_buffer_pool_dump_pct = 25 (was: 100)
|
innodb_buffer_pool_load_at_startup = ON (was: OFF)
|
innodb_checksum_algorithm = CRC32 (was: INNODB)
|
innodb_file_format = Barracuda (was: Antelope)
|
innodb_file_format_max = Barracuda (was: Antelope)
|
innodb_large_prefix = ON (was: OFF)
|
innodb_log_compressed_pages = ON (was: OFF)
|
innodb_purge_threads = 4 (was: 1)
|
innodb_strict_mode = ON (was: OFF)
|
|
|
binlog_annotate_row_events = ON (was: OFF)
|
binlog_format = MIXED (was: STATEMENT)
|
group_concat_max_len = 1M (was: 1025)
|
lock_wait_timeout = 86400(1day)(was: 1year)
|
log_slow_admin_statements = ON (was: OFF)
|
log_slow_slave_statements = ON (was: OFF)
|
log_warnings = 2 (was: 1)
|
max_allowed_packet = 16M (was: 4M)
|
replicate_annotate_row_events = ON (was: OFF)
|
slave_net_timeout = 60 (was: 3600)
|
sync_binlog = 1 (was: 0)
|
aria_recover = FORCE, BACKUP (was: NORMAL)
|
myisam_recover_options = FORCE, BACKUP (was: OFF)
|
Attachments
Issue Links
- includes
-
-
- Stalled
-
-
MDEV-8429 Change binlog_checksum default to match MySQL 5.6.6+
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Open
-
-
-
- Confirmed
-
-
-
- Closed
-
-
-
- Confirmed
-
-
-
- Closed
-
-
-
- Open
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Confirmed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Open
-
-
-
- Open
-
-
-
- Open
-
-
-
- Stalled
-
-
-
- Open
-
-
-
- Open
-
-
-
- Open
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
(34 relates to)
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
Poor MySQL has received some negative feedback over the years^1^^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand. Oracle are working on changing more defaults in 5.7^3^^4^^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html |
Poor MySQL has received some negative feedback over the years^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand. Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html |
| Description |
Poor MySQL has received some negative feedback over the years^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand. Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html |
Poor MySQL has received some negative feedback over the years ^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand. Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html |
| Priority | Trivial [ 5 ] | Major [ 3 ] |
| Fix Version/s | 10.2 [ 14601 ] |
| Workflow | MariaDB v2 [ 59824 ] | MariaDB v3 [ 62565 ] |
| Link |
This issue relates to |
| Assignee | Nirbhay Choubey [ nirbhay_c ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Sprint | 5.51 & 10.2 [ 85 ] |
| Rank | Ranked higher |
| Description |
Poor MySQL has received some negative feedback over the years ^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand. Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html |
Poor MySQL has received some negative feedback over the years ^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand.
Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html Proposed new defaults: {code} innodb_checksum_algorithm = CRC32 innodb_purge_threads = 4 innodb_strict_mode = ON innodb_buffer_pool_dump_at_shutdown = ON innodb_buffer_pool_load_at_startup = ON innodb_buffer_pool_dump_pct = 25 innodb_file_format = Barracuda innodb_large_prefix = ON sync_binlog = 1 slave_net_timeout = 60 binlog_format = ROW log_warnings = 2 log_slow_admin_statements = ON log_slow_slave_statements = ON log_queries_not_using_indexes = ON min-examined-row-limit = 1000 query_cache_strip_comments = ON TO BE DISCUSSED --------------- default_tmp_storage_engine = INNODB (Current default: Empty) innodb_log_compressed_pages = ON (It was turned back off in 10.1.2) table_definition_cache = -1 (autosized; Current default: 400) long-query-time = 2 (Current default: 10.0 group_concat_max_len = 1M (Current default: 1K) max_allowed_packet = 16M (Current default: 4M) innodb_autoinc_lock_mode = 2 (Required for Galera; Current default: 1) innodb_log_file_size = 128M (Current default: 48M) binlog_annotate_row_events = ON (Current default: OFF) replicate_annotate_row_events = ON (Current default: OFF) innodb_stats_traditional = OFF (Current default: ON) use_stat_tables = complementary (Current default: never) histogram_size = 255 (Current default: 0) aria_recover = QUICK, BACKUP (or FORCE, BACKUP; Current default: NORMAL) myisam_recover_options = QUICK, BACKUP (or FORCE, BACKUP; Current default: OFF) lower_case_table_names = 1 updatable_views_with_limit = OFF (Current default: ON) optimizer_switch = ?? sql_mode = ?? (Current default: NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION) lock_wait_timeout = ?? (Current default: 1 year) * sync_binlog currently set to 1 (from 0), Should we set it even higher? * Performance schema variables? * Disable query cache? {code} |
| Assignee | Nirbhay Choubey [ nirbhay_c ] | Daniel Black [ danblack ] |
| Assignee | Daniel Black [ danblack ] | Nirbhay Choubey [ nirbhay_c ] |
| Description |
Poor MySQL has received some negative feedback over the years ^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand.
Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html Proposed new defaults: {code} innodb_checksum_algorithm = CRC32 innodb_purge_threads = 4 innodb_strict_mode = ON innodb_buffer_pool_dump_at_shutdown = ON innodb_buffer_pool_load_at_startup = ON innodb_buffer_pool_dump_pct = 25 innodb_file_format = Barracuda innodb_large_prefix = ON sync_binlog = 1 slave_net_timeout = 60 binlog_format = ROW log_warnings = 2 log_slow_admin_statements = ON log_slow_slave_statements = ON log_queries_not_using_indexes = ON min-examined-row-limit = 1000 query_cache_strip_comments = ON TO BE DISCUSSED --------------- default_tmp_storage_engine = INNODB (Current default: Empty) innodb_log_compressed_pages = ON (It was turned back off in 10.1.2) table_definition_cache = -1 (autosized; Current default: 400) long-query-time = 2 (Current default: 10.0 group_concat_max_len = 1M (Current default: 1K) max_allowed_packet = 16M (Current default: 4M) innodb_autoinc_lock_mode = 2 (Required for Galera; Current default: 1) innodb_log_file_size = 128M (Current default: 48M) binlog_annotate_row_events = ON (Current default: OFF) replicate_annotate_row_events = ON (Current default: OFF) innodb_stats_traditional = OFF (Current default: ON) use_stat_tables = complementary (Current default: never) histogram_size = 255 (Current default: 0) aria_recover = QUICK, BACKUP (or FORCE, BACKUP; Current default: NORMAL) myisam_recover_options = QUICK, BACKUP (or FORCE, BACKUP; Current default: OFF) lower_case_table_names = 1 updatable_views_with_limit = OFF (Current default: ON) optimizer_switch = ?? sql_mode = ?? (Current default: NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION) lock_wait_timeout = ?? (Current default: 1 year) * sync_binlog currently set to 1 (from 0), Should we set it even higher? * Performance schema variables? * Disable query cache? {code} |
Poor MySQL has received some negative feedback over the years ^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand.
Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html Proposed new defaults: {code} innodb_checksum_algorithm = CRC32 innodb_purge_threads = 4 innodb_strict_mode = ON innodb_buffer_pool_dump_at_shutdown = ON innodb_buffer_pool_load_at_startup = ON innodb_buffer_pool_dump_pct = 25 innodb_file_format = Barracuda innodb_large_prefix = ON sync_binlog = 1 slave_net_timeout = 60 binlog_format = MIXED # (was ROW) MIXED format will be safer in traditional replication scenarios where master's still running with STMT. log_warnings = 2 log_slow_admin_statements = ON log_slow_slave_statements = ON log_queries_not_using_indexes = ON min-examined-row-limit = 1000 query_cache_strip_comments = ON TO BE DISCUSSED --------------- default_tmp_storage_engine = INNODB (Current default: Empty) innodb_log_compressed_pages = ON (It was turned back off in 10.1.2) table_definition_cache = -1 (autosized; Current default: 400) long-query-time = 2 (Current default: 10.0 group_concat_max_len = 1M (Current default: 1K) max_allowed_packet = 16M (Current default: 4M) innodb_autoinc_lock_mode = 2 (Required for Galera; Current default: 1) innodb_log_file_size = 128M (Current default: 48M) binlog_annotate_row_events = ON (Current default: OFF) replicate_annotate_row_events = ON (Current default: OFF) innodb_stats_traditional = OFF (Current default: ON) use_stat_tables = complementary (Current default: never) histogram_size = 255 (Current default: 0) aria_recover = QUICK, BACKUP (or FORCE, BACKUP; Current default: NORMAL) myisam_recover_options = QUICK, BACKUP (or FORCE, BACKUP; Current default: OFF) lower_case_table_names = 1 updatable_views_with_limit = OFF (Current default: ON) optimizer_switch = ?? sql_mode = ?? (Current default: NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION) lock_wait_timeout = ?? (Current default: 1 year) * sync_binlog currently set to 1 (from 0), Should we set it even higher? * Performance schema variables? * Disable query cache? {code} |
| Sprint | 5.5.51 & 10.2.2 [ 85 ] | 5.5.51 & 10.2.2, 10.2.2-1 [ 85, 89 ] |
| Rank | Ranked higher |
| Description |
Poor MySQL has received some negative feedback over the years ^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand.
Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html Proposed new defaults: {code} innodb_checksum_algorithm = CRC32 innodb_purge_threads = 4 innodb_strict_mode = ON innodb_buffer_pool_dump_at_shutdown = ON innodb_buffer_pool_load_at_startup = ON innodb_buffer_pool_dump_pct = 25 innodb_file_format = Barracuda innodb_large_prefix = ON sync_binlog = 1 slave_net_timeout = 60 binlog_format = MIXED # (was ROW) MIXED format will be safer in traditional replication scenarios where master's still running with STMT. log_warnings = 2 log_slow_admin_statements = ON log_slow_slave_statements = ON log_queries_not_using_indexes = ON min-examined-row-limit = 1000 query_cache_strip_comments = ON TO BE DISCUSSED --------------- default_tmp_storage_engine = INNODB (Current default: Empty) innodb_log_compressed_pages = ON (It was turned back off in 10.1.2) table_definition_cache = -1 (autosized; Current default: 400) long-query-time = 2 (Current default: 10.0 group_concat_max_len = 1M (Current default: 1K) max_allowed_packet = 16M (Current default: 4M) innodb_autoinc_lock_mode = 2 (Required for Galera; Current default: 1) innodb_log_file_size = 128M (Current default: 48M) binlog_annotate_row_events = ON (Current default: OFF) replicate_annotate_row_events = ON (Current default: OFF) innodb_stats_traditional = OFF (Current default: ON) use_stat_tables = complementary (Current default: never) histogram_size = 255 (Current default: 0) aria_recover = QUICK, BACKUP (or FORCE, BACKUP; Current default: NORMAL) myisam_recover_options = QUICK, BACKUP (or FORCE, BACKUP; Current default: OFF) lower_case_table_names = 1 updatable_views_with_limit = OFF (Current default: ON) optimizer_switch = ?? sql_mode = ?? (Current default: NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION) lock_wait_timeout = ?? (Current default: 1 year) * sync_binlog currently set to 1 (from 0), Should we set it even higher? * Performance schema variables? * Disable query cache? {code} |
Poor MySQL has received some negative feedback over the years ^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand.
Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html Proposed new defaults: {code} innodb_checksum_algorithm = CRC32 innodb_purge_threads = 4 innodb_strict_mode = ON innodb_buffer_pool_dump_at_shutdown = ON innodb_buffer_pool_load_at_startup = ON innodb_buffer_pool_dump_pct = 25 innodb_file_format = Barracuda innodb_large_prefix = ON sync_binlog = 1 (Current default: 0) slave_net_timeout = 60 (Current default: 3600) binlog_format = MIXED # (was ROW) MIXED format will be safer in traditional replication scenarios where master's still running with STMT. log_warnings = 2 (Current default: 1) log_slow_admin_statements = ON (Current default: OFF) log_slow_slave_statements = ON (Current default: OFF) log_queries_not_using_indexes = ON (Current default: OFF) min-examined-row-limit = 1000 (Current default: 0) query_cache_strip_comments = ON (Current default: OFF) TO BE DISCUSSED --------------- default_tmp_storage_engine = INNODB (Current default: Empty) innodb_log_compressed_pages = ON (It was turned back off in 10.1.2) table_definition_cache = -1 (autosized; Current default: 400) long-query-time = 2 (Current default: 10.0 group_concat_max_len = 1M (Current default: 1K) max_allowed_packet = 16M (Current default: 4M) innodb_autoinc_lock_mode = 2 (Required for Galera; Current default: 1) innodb_log_file_size = 128M (Current default: 48M) binlog_annotate_row_events = ON (Current default: OFF) replicate_annotate_row_events = ON (Current default: OFF) innodb_stats_traditional = OFF (Current default: ON) use_stat_tables = complementary (Current default: never) histogram_size = 255 (Current default: 0) aria_recover = QUICK, BACKUP (or FORCE, BACKUP; Current default: NORMAL) myisam_recover_options = QUICK, BACKUP (or FORCE, BACKUP; Current default: OFF) lower_case_table_names = 1 updatable_views_with_limit = OFF (Current default: ON) optimizer_switch = ?? sql_mode = ?? (Current default: NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION) lock_wait_timeout = ?? (Current default: 1 year) * sync_binlog currently set to 1 (from 0), Should we set it even higher? * Performance schema variables? * Disable query cache? {code} |
| Sprint | 5.5.51 & 10.2.2, 10.2.2-1 [ 85, 89 ] | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1 [ 85, 89, 102 ] |
| Rank | Ranked lower |
| Sprint | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1 [ 85, 89, 102 ] | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2 [ 85, 89, 102, 105 ] |
| Link |
This issue relates to |
| Link | This issue relates to MDEV-11040 [ MDEV-11040 ] |
| Link |
This issue relates to |
| Description |
Poor MySQL has received some negative feedback over the years ^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand.
Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html Proposed new defaults: {code} innodb_checksum_algorithm = CRC32 innodb_purge_threads = 4 innodb_strict_mode = ON innodb_buffer_pool_dump_at_shutdown = ON innodb_buffer_pool_load_at_startup = ON innodb_buffer_pool_dump_pct = 25 innodb_file_format = Barracuda innodb_large_prefix = ON sync_binlog = 1 (Current default: 0) slave_net_timeout = 60 (Current default: 3600) binlog_format = MIXED # (was ROW) MIXED format will be safer in traditional replication scenarios where master's still running with STMT. log_warnings = 2 (Current default: 1) log_slow_admin_statements = ON (Current default: OFF) log_slow_slave_statements = ON (Current default: OFF) log_queries_not_using_indexes = ON (Current default: OFF) min-examined-row-limit = 1000 (Current default: 0) query_cache_strip_comments = ON (Current default: OFF) TO BE DISCUSSED --------------- default_tmp_storage_engine = INNODB (Current default: Empty) innodb_log_compressed_pages = ON (It was turned back off in 10.1.2) table_definition_cache = -1 (autosized; Current default: 400) long-query-time = 2 (Current default: 10.0 group_concat_max_len = 1M (Current default: 1K) max_allowed_packet = 16M (Current default: 4M) innodb_autoinc_lock_mode = 2 (Required for Galera; Current default: 1) innodb_log_file_size = 128M (Current default: 48M) binlog_annotate_row_events = ON (Current default: OFF) replicate_annotate_row_events = ON (Current default: OFF) innodb_stats_traditional = OFF (Current default: ON) use_stat_tables = complementary (Current default: never) histogram_size = 255 (Current default: 0) aria_recover = QUICK, BACKUP (or FORCE, BACKUP; Current default: NORMAL) myisam_recover_options = QUICK, BACKUP (or FORCE, BACKUP; Current default: OFF) lower_case_table_names = 1 updatable_views_with_limit = OFF (Current default: ON) optimizer_switch = ?? sql_mode = ?? (Current default: NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION) lock_wait_timeout = ?? (Current default: 1 year) * sync_binlog currently set to 1 (from 0), Should we set it even higher? * Performance schema variables? * Disable query cache? {code} |
Poor MySQL has received some negative feedback over the years ^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand.
Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html Proposed new defaults: {code} innodb_checksum_algorithm = CRC32 innodb_purge_threads = 4 innodb_strict_mode = ON innodb_buffer_pool_dump_at_shutdown = ON innodb_buffer_pool_load_at_startup = ON innodb_buffer_pool_dump_pct = 25 innodb_file_format = Barracuda innodb_large_prefix = ON sync_binlog = 1 (Current default: 0) slave_net_timeout = 60 (Current default: 3600) binlog_format = MIXED # (was ROW) MIXED format will be safer in traditional replication scenarios where master's still running with STMT. log_warnings = 2 (Current default: 1) log_slow_admin_statements = ON (Current default: OFF) log_slow_slave_statements = ON (Current default: OFF) log_queries_not_using_indexes = ON (Current default: OFF) min-examined-row-limit = 1000 (Current default: 0) query_cache_strip_comments = ON (Current default: OFF) TO BE DISCUSSED --------------- default_tmp_storage_engine = INNODB (Current default: Empty) innodb_log_compressed_pages = ON (It was turned back off in 10.1.2) table_definition_cache = -1 (autosized; Current default: 400) long-query-time = 2 (Current default: 10.0 group_concat_max_len = 1M (Current default: 1K) max_allowed_packet = 16M (Current default: 4M) innodb_autoinc_lock_mode = 2 (Required for Galera; Current default: 1) innodb_log_file_size = 128M (Current default: 48M) binlog_annotate_row_events = ON (Current default: OFF) replicate_annotate_row_events = ON (Current default: OFF) innodb_stats_traditional = OFF (Current default: ON) use_stat_tables = complementary (Current default: never) histogram_size = 255 (Current default: 0) aria_recover = QUICK, BACKUP (or FORCE, BACKUP; Current default: NORMAL) myisam_recover_options = QUICK, BACKUP (or FORCE, BACKUP; Current default: OFF) lower_case_table_names = 2 updatable_views_with_limit = OFF (Current default: ON) optimizer_switch = ?? sql_mode = ?? (Current default: NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION) lock_wait_timeout = ?? (Current default: 1 year) * sync_binlog currently set to 1 (from 0), Should we set it even higher? * Performance schema variables? * Disable query cache? {code} |
| Description |
Poor MySQL has received some negative feedback over the years ^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand.
Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html Proposed new defaults: {code} innodb_checksum_algorithm = CRC32 innodb_purge_threads = 4 innodb_strict_mode = ON innodb_buffer_pool_dump_at_shutdown = ON innodb_buffer_pool_load_at_startup = ON innodb_buffer_pool_dump_pct = 25 innodb_file_format = Barracuda innodb_large_prefix = ON sync_binlog = 1 (Current default: 0) slave_net_timeout = 60 (Current default: 3600) binlog_format = MIXED # (was ROW) MIXED format will be safer in traditional replication scenarios where master's still running with STMT. log_warnings = 2 (Current default: 1) log_slow_admin_statements = ON (Current default: OFF) log_slow_slave_statements = ON (Current default: OFF) log_queries_not_using_indexes = ON (Current default: OFF) min-examined-row-limit = 1000 (Current default: 0) query_cache_strip_comments = ON (Current default: OFF) TO BE DISCUSSED --------------- default_tmp_storage_engine = INNODB (Current default: Empty) innodb_log_compressed_pages = ON (It was turned back off in 10.1.2) table_definition_cache = -1 (autosized; Current default: 400) long-query-time = 2 (Current default: 10.0 group_concat_max_len = 1M (Current default: 1K) max_allowed_packet = 16M (Current default: 4M) innodb_autoinc_lock_mode = 2 (Required for Galera; Current default: 1) innodb_log_file_size = 128M (Current default: 48M) binlog_annotate_row_events = ON (Current default: OFF) replicate_annotate_row_events = ON (Current default: OFF) innodb_stats_traditional = OFF (Current default: ON) use_stat_tables = complementary (Current default: never) histogram_size = 255 (Current default: 0) aria_recover = QUICK, BACKUP (or FORCE, BACKUP; Current default: NORMAL) myisam_recover_options = QUICK, BACKUP (or FORCE, BACKUP; Current default: OFF) lower_case_table_names = 2 updatable_views_with_limit = OFF (Current default: ON) optimizer_switch = ?? sql_mode = ?? (Current default: NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION) lock_wait_timeout = ?? (Current default: 1 year) * sync_binlog currently set to 1 (from 0), Should we set it even higher? * Performance schema variables? * Disable query cache? {code} |
Poor MySQL has received some negative feedback over the years ^1^ ^2^. As entertaining as it is watching and listening to developers struggle and whine, I think it's about time we changed some of the defaults and made the config easier to understand.
Oracle are working on changing more defaults in 5.7 ^3^ ^4^ ^5^, I think we should too. Something else they have done, is to radically change the simplicity of the default server config file, /etc/my.cnf: https://raw.githubusercontent.com/mysql/mysql-server/5.7/support-files/my-default.cnf.sh It's quite clear there, the sql_mode has been set, which will satisfy most developers and users looking for an ACID compliant database with little tweaking, and a rough note on increasing or decreasing RAM needed for InnoDB. MariaDB now probably needs something similar for Galera, CONNET and TokuDB. # http://sql-info.de/mysql/gotchas.html # http://blog.ionelmc.ro/2014/12/28/terrible-choices-mysql/ # http://www.tocker.ca/2015/01/23/proposal-to-change-additional-defaults-in-mysql-5-7.html # http://www.tocker.ca/2015/01/14/proposal-to-change-replication-and-innodb-settings-in-mysql-5-7.html # http://www.tocker.ca/2015/02/24/proposal-to-change-additional-defaults-in-mysql-5-7-february-edition.html Proposed new defaults: {code} innodb_autoinc_lock_mode = 2 (was: 1) innodb_buffer_pool_dump_at_shutdown = ON (was: OFF) innodb_buffer_pool_dump_pct = 25 (was: 100) innodb_buffer_pool_load_at_startup = ON (was: OFF) innodb_checksum_algorithm = CRC32 (was: INNODB) innodb_file_format = Barracuda (was: Antelope) innodb_file_format_max = Barracuda (was: Antelope) innodb_large_prefix = ON (was: OFF) innodb_log_compressed_pages = ON (was: OFF) innodb_purge_threads = 4 (was: 1) innodb_strict_mode = ON (was: OFF) binlog_annotate_row_events = ON (was: OFF) binlog_format = MIXED (was: STATEMENT) group_concat_max_len = 1M (was: 1025) lock_wait_timeout = 86400(1day)(was: 1year) log_slow_admin_statements = ON (was: OFF) log_slow_slave_statements = ON (was: OFF) log_warnings = 2 (was: 1) max_allowed_packet = 16M (was: 4M) replicate_annotate_row_events = ON (was: OFF) slave_net_timeout = 60 (was: 3600) sync_binlog = 1 (was: 0) aria_recover = FORCE, BACKUP (was: NORMAL) myisam_recover_options = FORCE, BACKUP (was: OFF) {code} |
| Priority | Major [ 3 ] | Blocker [ 1 ] |
| Link |
This issue relates to |
| Link |
This issue relates to |
| Link |
This issue relates to |
| Link |
This issue relates to |
| Sprint | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2 [ 85, 89, 102, 105 ] | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.0.28 [ 85, 89, 102, 105, 107 ] |
| Rank | Ranked higher |
| Sprint | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.0.28 [ 85, 89, 102, 105, 107 ] | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.1.19 [ 85, 89, 102, 105, 109 ] |
| Rank | Ranked higher |
| Link |
This issue relates to |
| Sprint | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.1.19 [ 85, 89, 102, 105, 109 ] | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-1 [ 85, 89, 102, 105, 110 ] |
| Rank | Ranked lower |
| Link |
This issue relates to |
| Sprint | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-1 [ 85, 89, 102, 105, 110 ] | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-2 [ 85, 89, 102, 105, 113 ] |
| Rank | Ranked lower |
| Link |
This issue relates to |
| Sprint | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-2 [ 85, 89, 102, 105, 113 ] | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-3 [ 85, 89, 102, 105, 115 ] |
| Rank | Ranked higher |
| Sprint | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-3 [ 85, 89, 102, 105, 115 ] | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-4 [ 85, 89, 102, 105, 117 ] |
| Rank | Ranked higher |
| Sprint | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-4 [ 85, 89, 102, 105, 117 ] | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-4, 10.2.4-1 [ 85, 89, 102, 105, 117, 121 ] |
| Rank | Ranked lower |
| Link |
This issue relates to |
| Link | This issue relates to MDEV-11592 [ MDEV-11592 ] |
| Sprint | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-4, 10.2.4-1 [ 85, 89, 102, 105, 117, 121 ] | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-4, 10.2.4-1, 10.2.4-5 [ 85, 89, 102, 105, 117, 121, 125 ] |
| Link | This issue relates to MDEV-11666 [ MDEV-11666 ] |
| Link |
This issue relates to |
| Link | This issue relates to MDEV-11691 [ MDEV-11691 ] |
| Sprint | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-4, 10.2.4-1, 10.2.4-5 [ 85, 89, 102, 105, 117, 121, 125 ] | 5.5.51 & 10.2.2, 10.2.2-1, 10.2.3-1, 10.2.3-2, 10.2.4-4, 10.2.4-1, 10.2.4-5, 10.0.29 [ 85, 89, 102, 105, 117, 121, 125, 128 ] |
| Rank | Ranked higher |
| Link |
This issue relates to |
| Link | This issue relates to MDEV-11822 [ MDEV-11822 ] |
| Labels | 10.2-rc |
| Link |
This issue relates to |
| Link | This issue relates to MDEV-11893 [ MDEV-11893 ] |
| Link | This issue relates to MDEV-11892 [ MDEV-11892 ] |
| Link | This issue relates to MDEV-11891 [ MDEV-11891 ] |
| Link | This issue relates to MDEV-11890 [ MDEV-11890 ] |
| Link | This issue relates to MDEV-11888 [ MDEV-11888 ] |
| Link | This issue relates to MDEV-11876 [ MDEV-11876 ] |
| Link | This issue relates to MDEV-11875 [ MDEV-11875 ] |
| Link |
This issue relates to |
| Link |
This issue relates to |
| Link |
This issue relates to |
| Link |
This issue relates to |
| Component/s | Server [ 13907 ] | |
| Fix Version/s | 10.2.4 [ 22116 ] | |
| Fix Version/s | 10.2 [ 14601 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Link |
This issue is duplicated by |
| Link |
This issue relates to |
| Workflow | MariaDB v3 [ 62565 ] | MariaDB v4 [ 132526 ] |