Category Archives: Community

MySQL 5.6.17 Community Release Notes

Thank you to the MySQL Community, on behalf of the MySQL team @ Oracle. Your bug reports, testcases and patches have helped create a better MySQL 5.6.17. In particular: Thanks to Anthony Pong for reporting a confusing error message when mysql_install_db could not locate the required Perl modules. Bug #69844. Thanks to Jervin Real for […]

Plan to remove unused command line programs (10 out of 43)

Have you ever noticed the vast number of command line programs that ship with MySQL? Here is an ls from MySQL 5.6.16′s bin directory: morgo@Rbook:~/Documents/mysql-installs/5.6.16/bin$ ls innochecksum msql2mysql my_print_defaults myisam_ftdump myisamchk myisamlog myisampack mysql mysql_client_test mysql_client_test_embedded mysql_config mysql_config_editor mysql_convert_table_format mysql_embedded mysql_find_rows mysql_fix_extensions mysql_plugin mysql_secure_installation mysql_setpermission mysql_tzinfo_to_sql mysql_upgrade mysql_waitpid mysql_zap mysqlaccess mysqlaccess.conf mysqladmin mysqlbinlog mysqlbug mysqlcheck […]

A followup on SHOW ENGINE INNODB MUTEX

In November, I wrote about the command SHOW ENGINE INNODB MUTEX and sought feedback as to how it continues to be used post introduction of performance_schema. The outcome from this feedback is that the MySQL team has decided to remove this command from MySQL 5.7. These decisions are not light ones for the team to […]

MySQL 5.6.16 Community Release Notes

Thank you to the MySQL Community, on behalf of the MySQL team @ Oracle. Your bug reports, testcases and patches have helped create a better MySQL 5.6.16. In particular: Thanks to Honza Horak for suggesting we make tmpdir configurable at build-time, and for providing a patch. Bug #68338. Thanks to Hartmut Holzgraefe for reporting a […]

Proposal to enable sql mode ONLY_FULL_GROUP_BY by default

We are considering enabling the SQL mode ONLY_FULL_GROUP_BY by default in MySQL 5.7. Here is a quick example to demonstrate how this change will impact you: Sample Data: CREATE TABLE invoice_line_items (id INT NOT NULL PRIMARY KEY auto_increment, invoice_id INT NOT NULL, description varchar(100) ); INSERT INTO invoice_line_items VALUES (NULL, 1, ‘New socks’), (NULL, 1, […]

Spring cleaning MySQL bugs

The MySQL team has been busy fixing bugs and sorting through older bugs. To give you a couple of recent stats: Norvald blogged about 14 bugs fixed at the request of Linux Distributions. Tomas Ulin’s keynote at Percona Live mentioned 1991 Bugs Fixed in 5.6, with 3763 Bugs Fixed in Total Since MySQL 5.5 GA […]

Making strict sql_mode the default

MySQL has sometimes faced criticism for being too relaxed at allowing invalid values, or inserting but truncating values that are out of range. For example: mysql> CREATE TABLE unsigned_int (a int unsigned); Query OK, 0 rows affected (0.03 sec) mysql> INSERT INTO unsigned_int (a) VALUES (-1); Query OK, 1 row affected, 1 warning (0.01 sec) […]

Proposal to change MySQL replication defaults

In the MySQL team @ Oracle, we’ve been discussing changing the default values for MySQL replication so that they are safer to use. Specifically: Setting Current Value Proposed New Value sync_binlog 0 1 master-info-repository FILE TABLE relay-log-info-repository FILE TABLE I have written about all of these settings before in my post on deciding whether or […]

MySQL 5.6.15 Community Release Notes

Thank you to the MySQL Community, on behalf of the MySQL team @ Oracle. Your bug reports, testcases and patches have helped create a better MySQL 5.6.15. In particular: Thanks to Yoshinori Matsunobu, who reported that the performance_schema did not instrument locks related to semisync replication. Bug #70577. Thanks to Sebastian Strzelczyk, who reported excessive […]