MySQL 8.0

MySQL 8.0

PREVIOUS POST
NEXT POST

MySQL 8.0

If you haven’t heard the news yet, MySQL 8.0 is apparently the next release of the world-famous database server.

Obviously abandoning plans to name the next release 5.8, Percona Server’s upstream provider relabelled all 5.8-related bugs to 8.0 as follows:

Reported version value updated to reflect release name change from 5.8 to 8.0

What will MySQL 8.0 bring to the world?

While lossless RBR has been suggested by Simon Mudd (for example), the actual feature list (except a Boost 1.60.0 upgrade!) remains a secret.

As far as bug and feature requests go, a smart google query revealed which bugs are likely to be fixed in (or are feature requests for) MySQL 8.0.

Here is the full list:

  • MySQL Bug #79380: Upgrade to Boost 1.60.0
  • MySQL Bug #79037: get rid of dynamic_array in st_mysql_options
  • MySQL Bug #80793: EXTEND EXPLAIN to cover ALTER TABLE
  • MySQL Bug #79812: JSON_ARRAY and JSON_OBJECT return …
  • MySQL Bug #79666: fix errors reported by ubsan
  • MySQL Bug #79463: Improve P_S configuration behaviour
  • MySQL Bug #79939: default_password_lifetime > 0 should print …
  • MySQL Bug #79330: DROP TABLESPACE fails for missing general …
  • MySQL Bug #80772: Excessive memory used in memory/innodb …
  • MySQL Bug #80481: Accesses to new data-dictionary add confusing …
  • MySQL Bug #77712: mysql_real_query does not report an error for …
  • MySQL Bug #79813: Boolean values are returned inconsistently with …
  • MySQL Bug #79073: Optimizer hint to disallow full scan
  • MySQL Bug #77732: REGRESSION: replication fails for insufficient …
  • MySQL Bug #79076: make hostname a dynamic variable
  • MySQL Bug #78978: Add microseconds support to UNIX_TIMESTAMP
  • MySQL Bug #77600: Bump major version of libmysqlclient in 8.0
  • MySQL Bug #79182: main.help_verbose failing on freebsd
  • MySQL Bug #80627: incorrect function referenced in spatial error …
  • MySQL Bug #80372: Built-in mysql functions are case sensitive …
  • MySQL Bug #79150: InnoDB: Remove runtime checks for 32-bit file …
  • MySQL Bug #76918: Unhelpful error for mysql_ssl_rsa_setup when …
  • MySQL Bug #80523: current_memory in sys.session can go negative!
  • MySQL Bug #78210: SHUTDOWN command should have an option …
  • MySQL Bug #80823: sys should have a mdl session oriented view
  • MySQL Bug #78374: “CREATE USER IF NOT EXISTS” reports an error
  • MySQL Bug #79522: can mysqldump print the fully qualified table …
  • MySQL Bug #78457: Use gettext and .po(t) files for translations
  • MySQL Bug #78593: mysqlpump creates incorrect ALTER TABLE …
  • MySQL Bug #78041: GROUP_CONCAT() truncation should be an …
  • MySQL Bug #76927: Duplicate UK values in READ-COMMITTED …
  • MySQL Bug #77997: Automatic mysql_upgrade
  • MySQL Bug #78495: Table mysql.gtid_executed cannot be opened.
  • MySQL Bug #78698: Simple delete query causes InnoDB: Failing …
  • MySQL Bug #76392: Assume that index_id is unique within a …
  • MySQL Bug #76671: InnoDB: Assertion failure in thread 19 in file …
  • MySQL Bug #76803: InnoDB: Unlock row could not find a 2 mode …
  • MySQL Bug #78527: incomplete support and/or documentation of …
  • MySQL Bug #78732: InnoDB: Failing assertion: *mbmaxlen < 5 in file …
  • MySQL Bug #76356: Reduce header file dependencies for …
  • MySQL Bug #77056: There is no clear error message if …
  • MySQL Bug #76329: COLLATE option not accepted in generated …
  • MySQL Bug #79500: InnoDB: Assertion failure in thread …
  • MySQL Bug #72284: please use better options to …
  • MySQL Bug #78397: Subquery Materialization on DELETE WHERE …
  • MySQL Bug #76552: Cannot shutdown MySQL using JDBC driver
  • MySQL Bug #76532: MySQL calls exit(MYSQLD_ABORT_EXIT …
  • MySQL Bug #76432: handle_fatal_signal (sig=11) in …
  • MySQL Bug #41925: Warning 1366 Incorrect string value: … for …
  • MySQL Bug #78452: Alter table add virtual index hits assert in …
  • MySQL Bug #77097: InnoDB Online DDL should support change …
  • MySQL Bug #77149: sys should possibly offer user threads …
PREVIOUS POST
NEXT POST

Share this post

Comments (11)

  • Morgan Tocker Reply

    Hi Roel,

    In terms of what’s coming, the best place is to look at our labs and presentations (from Percona Live in Santa Clara, OOW2016, and we’ve submitted quite a number of talks for PL Amsterdam 🙂 This gives quite a good overview of what the team is actively working on.

    To highlight a couple of core changes not in your list:

    1) We are working on replacing the .frm files used for data dictionary with a native implementation based on InnoDB. You can read more about the motivations behind this here:
    http://www.tocker.ca/2014/07/30/beyond-the-frm-ideas-for-a-native-mysql-data-dictionary.html
    http://mysqlserverteam.com/a-new-data-dictionary-for-mysql/
    http://mysqlserverteam.com/a-preview-on-lab-release-with-new-data-dictionary-in-mysql/

    2) The optimizer team is continuing to work on parser and cost model refactoring. Some of this work hit 5.7, but one of the changes I’m looking forward is cost-based estimates that understand how much of the index is in memory.

    – Morgan (PM for the MySQL Server)

    July 5, 2016 at 9:18 pm
  • Fadi El-Eter (itoctopus) Reply

    I hope MySQL won’t go the FireFox way when naming their versions, or we’ll end up with something like “MySQL version 47.0”, the same way I have FireFox version 47.0 on my machine. It’s not important but it just looks weird.

    July 7, 2016 at 8:35 am
  • emily ikuta Reply

    Question on twitter from @min0lta “MySQL 8.0? Is it the truth? @Percona I can’t search more info about it.”

    July 11, 2016 at 11:01 am
    • Roel Van de Paar Reply

      Emily, please see the Google link above and Morgan (PM for the MySQL Server)’s input.

      July 12, 2016 at 11:24 pm
  • krzysiunet Reply

    Foobar x.y will have next version Foobar (y+1).0. PHP 5.6 to 7.0. MySQL 5.7 to 8.0.

    November 4, 2016 at 11:00 pm
    • Roel Van de Paar Reply

      x+1 you mean? 😉

      November 6, 2016 at 6:47 pm
    • Mark Garrett Reply

      Well, technically, they went to 7.0 because they wanted to skip PHP 6 (big brouhaha about that) . It just so happened that the last 5.x version was .6.

      January 12, 2017 at 2:29 pm
  • Roel Van de Paar Reply

    Oh wait, I see what you mean 🙂 Nice formula 🙂

    November 6, 2016 at 6:47 pm

Leave a Reply