In MySQL 5.6 we increased the max_allowed_packet from 1M to a conservative 4M.We would like to thank Shlomi Noach for this suggestion. We also believe that the default maximum length for grouping values has not kept pace with the larger amounts of memory available on modern hardware. We find the GROUP_CONCAT() function in MySQL to be incredibly useful for summarizing results in an aggregate query.We would like to thank Ryuta Kamizono for this suggestion. This behavior applies to both interactive and batch modes, and can be disabled with show_warnings=0. We feel like ON is the more useful default, as a user will typically not intend to execute statements that cause warnings. The MySQL command line client has the ability to automatically print warnings out to screen as they occur.We would like to thank Daniel Black for suggesting we change our slow query log options. We also considered that setting the min-examined-row-limit to a non zero value will now require an additional step for those that set their long-query-time to zero seconds. Our own MySQL Enterprise Monitor considers 100ms acceptable, and 400ms (4x) as slow. A popular web performance tool uses a default of 0.5 seconds for an acceptable time to render a full page server side, with 2 seconds (4x) slow enough to warrant logging. In proposing this change, we considered the defaults that other products use for considering a query slow. The number of 1000 was chosen because it should eliminate the majority of false positives from queries retrieving a static set of records such as navigation menu items, which are well suited to tablescans. A query exceeding 2 seconds will now be considered slow, and since queries that do not use indexes have the highest chance of causing future problems, they will also be logged unless they examine fewer than 1000 rows. The slow query log remains disabled by default, but when enabled our hope is that we can make it immediately useful.To explain these changes in more details: jason on MySQL 5.6.24 Community Release Notesįollowing on from my two earlier posts, in the MySQL team we are proposing a new set of changes to defaults for MySQL 5.7: Setting.jason on Moving to Product Management & European Tour.jason on Proposal to enable sql mode ONLY_FULL_GROUP_BY by default.Prince PK on MySQL 5.6.24 Community Release Notes.Brett Symbarashey Jaggz Jongwe on Five reasons why vertical scalability matters.Proposal to extend binary operators in MySQL.What would you like to see in MySQL 5.8?.
MySQL Community Reception at Oracle OpenWorld.Moving to Product Management & European Tour.My current position has me responsible for MySQL Server product management.
0 kommentar(er)
