6 ms·

MySQL 5.7.6 is out

72 points by porker 12y ago

spacemanmatt 12y ago
For the effort to absorb "big changes" I would also weigh porting to PostgreSQL.
- VLM 12y ago
  Its clickbait headline, or maybe they're going for outright sarcasm given how little is changing. Technically its true that the install process is a little different but not much, and theres some minor changes in user configuration. I've looked into it and the most exciting "DBA level" changes are YEAR(2) is finally utterly expunged, and there's some new reserved words "NONBLOCKING" and "OPTIMIZERCOSTS". Thats about as exciting as it gets. Its not transparent upgrade but its not like they're changing the default db engine to an embedded nosql engine, or changing the default char encoding to EBCDIC.
  - morgo 12y ago
    I would say the biggest change is that the default SQL mode will be the equivalent to 5.6's ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION,ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE,NO_ZERO_IN_DATE,NO_AUTO_CREATE_USER. This means that a number of statements that produced warnings (but proceeded) will now produce errors. I have some slides on it here: http://www.slideshare.net/morgo/upcoming-changes-in-mysql-57 http://www.slideshare.net/morgo/upcoming-changes-in-mysql-57 (see slide 33 onwards).
joshstrange 12y ago
MySQL doesn't excite me at all anymore. It used to be my DB of choice but as of late I've been using postgres and other than tools being somewhat lacking (this is getting better all the time, there are now GUI browsers for postgres that rival sequel pro). Nothing was really keeping me on MySQL other than it was generally the prefered DB for most OS projects and I had used it in professional settings multiple times. Postgres's JSON store is very interesting and I've read a number of articles on other cool things in Postgres all while MySQL was more or less silent. I'd love to setup a postgres server at work and benchmark it against our MySQL DB, the one thing really holding me back is our use of ENUMs but I don't think that's going to be a big barrier and I hate them anyways.
- pilif 12y ago
  > the one thing really holding me back is our use of ENUMs but I don't think that's going to be a big barrier and I hate them anyways Postgres has proper support for ENUM as defined in the SQL Standard. You have to create a new type and declare it as being an ENUM type: http://www.postgresql.org/docs/9.4/static/datatype-enum.html http://www.postgresql.org/docs/9.4/static/datatype-enum.html
  - joshstrange 12y ago
    Very interesting! Thanks for the link, even with that I'd rather convert the ENUMs to just VARCHARs as our MVC framework doesn't support ENUMs but it "Just works" because it sends strings to MySQL and MySQL stores them as INTs that map to ENUM values. Because of this the test framework never played nice with creating test DB's that used ENUMs.
- recibe 12y ago
  Postgres' ecosystem is a joke compared to mysql's. Just try finding a: - mysql-to-postgres import tool - mysql workbench for postgres (pgadmin is terrible) - phpmyadmin replacement for postgres (phpPgAdmin is terrible)
- eropple 12y ago
  I know what you're saying, but when I hear people being excited about data stores, I get a little worried. (Being excited about data stores gave us the rise of MongoDB. MySQL tables corrupting because you used MyISAM like a well-intentioned fool is "exciting", too.) I've moved to Postgres for most things because it's not at all exciting for the majority of use cases. It does a thing, does it well, and doesn't break. I honestly can't say the same about MySQL.
  - joshstrange 12y ago
    Yes, "Excite" is probably not the right word to use there. I share a wariness towards too much "excitement" about a new DB (I never really trusted Mongo and only used it to play with). In this case I don't see postgres as "new and unproven" but rather "proven and pushing the envelope" which is what excites me.
taf2 12y ago
So much MySQL hate these days... I should try Postgres out but here's why I still like and trust MySQL or MariaDB/Percona... 1. It's reliable/durable 2. I know the tools (mysql command line is friendly to me) 3. It's performance is predictable. 99% of issues with performance are easily solved with the right index 4. I don't find myself needing many SQL features beyond the basics. Also, I'm a happy user of other tools to compliant mysql. Including redis and elasticsearch. Both of these tools IMO compliant MySQL. I'm no fan of Oracle by any means but at least MySQL is still an open source database. Perhaps when I have free time before the next startup I'll give Postgres a good look. For now I'll probably try it out with AWS redshift...
- Thaxll 12y ago
  Well it's HN, outside of Postgres / Redis everything sucks. And yes you're right on MySQL it's reliable. Honest question here, is there an equivalent of Percona tools for Postregres?
- pilif 12y ago
  >1. It's reliable/durable I would personally contest that. I've seen MySQL corrupt tables before and the insanely unhelpful defaults which make MySQL accept and alter invalid data really don't strike me as neither reliable nor durable. Your other points are valid reasons for sticking with MySQL though. If you're happy and the tool does what you need, that's fine. But once you've seen what you can do as you gain access to the more advanced SQL features and once you've burned by MySQL not starting up because of data corruption, then you might want to investigate other options. Postgres happens to be a very good alternative with good tools, predictable performance, very advanced SQL features, but also really good reliability and durability.
  - morgo 12y ago
    In the context of this post (MySQL 5.7) it does not accept invalid data :) The default sql mode has changed.
    - tsuraan 12y ago
morgo 12y ago
Community Manager for MySQL here! A better overview link for what's new in 5.7.6 specifically is this one: http://mysqlserverteam.com/the-mysql-5-7-6-milestone-release-is-available/ http://mysqlserverteam.com/the-mysql-5-7-6-milestone-release... To understand what's new in 5.7 overall: http://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html http://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html Specific to this blog post. Here is the page on upgrading: http://dev.mysql.com/doc/refman/5.7/en/upgrading-from-previous-series.html http://dev.mysql.com/doc/refman/5.7/en/upgrading-from-previo... I'm happy to answer any questions, please feel free to ask away.
- jordigh 12y ago
  > Community Manager for MySQL here! I always found this title a bit weird. How does one exactly manage a community? :-) https://plus.google.com/+AaronSeigo/posts/DHEx1tu5dSK https://plus.google.com/+AaronSeigo/posts/DHEx1tu5dSK
  - morgo 12y ago
    Please see my comments on this thread: https://news.ycombinator.com/item?id=8318199 https://news.ycombinator.com/item?id=8318199 I agree it's a silly name, but it's not like we created it :)
    - ddorian43 12y ago
      Click on the datetime of the comment to get the correct comment-link: https://news.ycombinator.com/item?id=8318807 https://news.ycombinator.com/item?id=8318807
    - j_s 12y ago
      If you've not heard of the term 'tummler' this might be helpful: To build a strong community, stop “community managing”, be a Tummler instead. http://dangerouslyawesome.com/2014/04/community-management-tummling-a-tale-of-two-mindsets/ http://dangerouslyawesome.com/2014/04/community-management-t...
deleted 12y ago
[deleted]
mootothemax 12y ago
There's one very important reason that I always return to MySQL: - If something goes wrong at 3am, I know how to fix it. Whether it's performance, server setup, or weird edge cases, I have it covered. This being the sole reason, does anyone have any "when you're in trouble" guides for Postgres or others?
hit8run 12y ago
How stable is it? When is it supposed to be used in production?
- morgo 12y ago
  5.7.6 is what we call a "Development Milestone Release", and is stated to be of approximately release candidate quality. We do not have a release date, but we're committed to a 2-3 year release cycle, with 5.6 being the last release in Feb 2013.
jordigh 12y ago
Dear lazyweb, How active is the MariaDB development compared to MySQL's? Should we still be concerned with Oracle trying to kill MySQL? How has that whole debacle played out?
- morgo 12y ago
  Edward Screven addresses this point in this video: https://www.youtube.com/watch?v=fzCpd4j72jA https://www.youtube.com/watch?v=fzCpd4j72jA - Oracle sees MySQL users as a distinct group of customers from the Oracle Database - 5 years on, the engineering team on MySQL is 2x what it was when acquired. By a simple metric (LoC), MySQL 5.6 has a larger delta than any previous release: https://www.flamingspork.com/blog/2013/03/05/mysql-code-size/ https://www.flamingspork.com/blog/2013/03/05/mysql-code-size... Edit: See also this interview with Percona's CEO - http://www.zdnet.com/article/mysql-why-the-open-source-database-is-better-off-under-oracle/ http://www.zdnet.com/article/mysql-why-the-open-source-datab...
  - jordigh 12y ago
    And I unlazied myself a little and found this: https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-features/ https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-features/ If marketing is to be believed, it does seem like MariaDB offers many points of attraction over MySQL. The fact that Oracle does not provide test cases or has proprietary extensions is a bit alarming from a software freedom perspective.
jkoudys 12y ago
> The main effort of the team has been focused on speed, with performance reportedly improved from 2 to 3 times compared to previous releases. Definitely good news, as MySQL came out during the peak of Moore's-law (or, more appropriately, a misapplication of) fueled idiocy where nobody seemed interested in investing in better performing software, since they all expected they'd have faster hardware next year. Now everybody's deploying to VPSes, so it's once again important that we get the most out of every single CPU cycle. I haven't gone through all the diffs, but if they're promising 2x to 3x improved performance, there must have been some pretty fundamental rewrites of old code. Coming from the Oracle + DB2 world, what I'd really like to see is some improved performance analysis and query optimization tools. There have been some incremental improvements to EXPLAIN (the new 'EXPLAIN on a named connection' feature seems pretty cool for when I have 10+ application instances all connecting to my DB), but it's still got a long way to go.
- morgo 12y ago
  I totally hear you here :) Visibility is the most useful and always under-rated feature. If I can clarify some of the recent enhancements here: - MySQL 5.6 introduced `EXPLAIN FORMAT=JSON`. MySQL Workbench uses this to visualize query plans (important as they get complicated.) - Also in 5.6 was optimizer trace (find out why indexes were not used etc.) and performance_schema enabled by default. - MySQL 5.7 adds cost information to `EXPLAIN FORMAT=JSON` (Workbench also understands it.) - Workbench also has a set of performance views based on Performance_schema (based on a project called SYS). You can install it as standalone from here too: https://github.com/MarkLeith/mysql-sys https://github.com/MarkLeith/mysql-sys - The runtime performance data from SYS is very useful for making correct optimization decisions. Being an SQL interface is also friendly for writing your own scripts against it. Also, to clarify on your first paragraph: Yes, refactoring old code was one of the ways this was achieved. We picked refactoring targets based on performance and because some of the older code is not very testable.
dschiptsov 12y ago
multiple page cleaner threads - this is nice.
deleted 12y ago
[deleted]

MySQL 5.7.6 is out

72 points by porker 12y ago

spacemanmatt 12y ago

For the effort to absorb "big changes" I would also weigh porting to PostgreSQL.

VLM 12y ago
Its clickbait headline, or maybe they're going for outright sarcasm given how little is changing. Technically its true that the install process is a little different but not much, and theres some minor changes in user configuration. I've looked into it and the most exciting "DBA level" changes are YEAR(2) is finally utterly expunged, and there's some new reserved words "NONBLOCKING" and "OPTIMIZERCOSTS". Thats about as exciting as it gets. Its not transparent upgrade but its not like they're changing the default db engine to an embedded nosql engine, or changing the default char encoding to EBCDIC.
- morgo 12y ago
  I would say the biggest change is that the default SQL mode will be the equivalent to 5.6's ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION,ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE,NO_ZERO_IN_DATE,NO_AUTO_CREATE_USER. This means that a number of statements that produced warnings (but proceeded) will now produce errors. I have some slides on it here: http://www.slideshare.net/morgo/upcoming-changes-in-mysql-57 http://www.slideshare.net/morgo/upcoming-changes-in-mysql-57 (see slide 33 onwards).

joshstrange 12y ago

MySQL doesn't excite me at all anymore. It used to be my DB of choice but as of late I've been using postgres and other than tools being somewhat lacking (this is getting better all the time, there are now GUI browsers for postgres that rival sequel pro). Nothing was really keeping me on MySQL other than it was generally the prefered DB for most OS projects and I had used it in professional settings multiple times. Postgres's JSON store is very interesting and I've read a number of articles on other cool things in Postgres all while MySQL was more or less silent. I'd love to setup a postgres server at work and benchmark it against our MySQL DB, the one thing really holding me back is our use of ENUMs but I don't think that's going to be a big barrier and I hate them anyways.

pilif 12y ago
> the one thing really holding me back is our use of ENUMs but I don't think that's going to be a big barrier and I hate them anyways Postgres has proper support for ENUM as defined in the SQL Standard. You have to create a new type and declare it as being an ENUM type: http://www.postgresql.org/docs/9.4/static/datatype-enum.html http://www.postgresql.org/docs/9.4/static/datatype-enum.html
- joshstrange 12y ago
  Very interesting! Thanks for the link, even with that I'd rather convert the ENUMs to just VARCHARs as our MVC framework doesn't support ENUMs but it "Just works" because it sends strings to MySQL and MySQL stores them as INTs that map to ENUM values. Because of this the test framework never played nice with creating test DB's that used ENUMs.
recibe 12y ago
Postgres' ecosystem is a joke compared to mysql's. Just try finding a: - mysql-to-postgres import tool - mysql workbench for postgres (pgadmin is terrible) - phpmyadmin replacement for postgres (phpPgAdmin is terrible)
eropple 12y ago
I know what you're saying, but when I hear people being excited about data stores, I get a little worried. (Being excited about data stores gave us the rise of MongoDB. MySQL tables corrupting because you used MyISAM like a well-intentioned fool is "exciting", too.) I've moved to Postgres for most things because it's not at all exciting for the majority of use cases. It does a thing, does it well, and doesn't break. I honestly can't say the same about MySQL.
- joshstrange 12y ago
  Yes, "Excite" is probably not the right word to use there. I share a wariness towards too much "excitement" about a new DB (I never really trusted Mongo and only used it to play with). In this case I don't see postgres as "new and unproven" but rather "proven and pushing the envelope" which is what excites me.

taf2 12y ago

So much MySQL hate these days... I should try Postgres out but here's why I still like and trust MySQL or MariaDB/Percona... 1. It's reliable/durable 2. I know the tools (mysql command line is friendly to me) 3. It's performance is predictable. 99% of issues with performance are easily solved with the right index 4. I don't find myself needing many SQL features beyond the basics. Also, I'm a happy user of other tools to compliant mysql. Including redis and elasticsearch. Both of these tools IMO compliant MySQL. I'm no fan of Oracle by any means but at least MySQL is still an open source database. Perhaps when I have free time before the next startup I'll give Postgres a good look. For now I'll probably try it out with AWS redshift...

Thaxll 12y ago
Well it's HN, outside of Postgres / Redis everything sucks. And yes you're right on MySQL it's reliable. Honest question here, is there an equivalent of Percona tools for Postregres?
pilif 12y ago
>1. It's reliable/durable I would personally contest that. I've seen MySQL corrupt tables before and the insanely unhelpful defaults which make MySQL accept and alter invalid data really don't strike me as neither reliable nor durable. Your other points are valid reasons for sticking with MySQL though. If you're happy and the tool does what you need, that's fine. But once you've seen what you can do as you gain access to the more advanced SQL features and once you've burned by MySQL not starting up because of data corruption, then you might want to investigate other options. Postgres happens to be a very good alternative with good tools, predictable performance, very advanced SQL features, but also really good reliability and durability.
- morgo 12y ago
  In the context of this post (MySQL 5.7) it does not accept invalid data :) The default sql mode has changed.
  - tsuraan 12y ago

morgo 12y ago

Community Manager for MySQL here! A better overview link for what's new in 5.7.6 specifically is this one: http://mysqlserverteam.com/the-mysql-5-7-6-milestone-release-is-available/ http://mysqlserverteam.com/the-mysql-5-7-6-milestone-release... To understand what's new in 5.7 overall: http://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html http://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html Specific to this blog post. Here is the page on upgrading: http://dev.mysql.com/doc/refman/5.7/en/upgrading-from-previous-series.html http://dev.mysql.com/doc/refman/5.7/en/upgrading-from-previo... I'm happy to answer any questions, please feel free to ask away.

jordigh 12y ago
> Community Manager for MySQL here! I always found this title a bit weird. How does one exactly manage a community? :-) https://plus.google.com/+AaronSeigo/posts/DHEx1tu5dSK https://plus.google.com/+AaronSeigo/posts/DHEx1tu5dSK
- morgo 12y ago
  Please see my comments on this thread: https://news.ycombinator.com/item?id=8318199 https://news.ycombinator.com/item?id=8318199 I agree it's a silly name, but it's not like we created it :)
  - ddorian43 12y ago
    Click on the datetime of the comment to get the correct comment-link: https://news.ycombinator.com/item?id=8318807 https://news.ycombinator.com/item?id=8318807
  - j_s 12y ago
    If you've not heard of the term 'tummler' this might be helpful: To build a strong community, stop “community managing”, be a Tummler instead. http://dangerouslyawesome.com/2014/04/community-management-tummling-a-tale-of-two-mindsets/ http://dangerouslyawesome.com/2014/04/community-management-t...

deleted 12y ago

[deleted]

mootothemax 12y ago

There's one very important reason that I always return to MySQL: - If something goes wrong at 3am, I know how to fix it. Whether it's performance, server setup, or weird edge cases, I have it covered. This being the sole reason, does anyone have any "when you're in trouble" guides for Postgres or others?

hit8run 12y ago

How stable is it? When is it supposed to be used in production?

morgo 12y ago
5.7.6 is what we call a "Development Milestone Release", and is stated to be of approximately release candidate quality. We do not have a release date, but we're committed to a 2-3 year release cycle, with 5.6 being the last release in Feb 2013.

jordigh 12y ago

Dear lazyweb, How active is the MariaDB development compared to MySQL's? Should we still be concerned with Oracle trying to kill MySQL? How has that whole debacle played out?

morgo 12y ago
Edward Screven addresses this point in this video: https://www.youtube.com/watch?v=fzCpd4j72jA https://www.youtube.com/watch?v=fzCpd4j72jA - Oracle sees MySQL users as a distinct group of customers from the Oracle Database - 5 years on, the engineering team on MySQL is 2x what it was when acquired. By a simple metric (LoC), MySQL 5.6 has a larger delta than any previous release: https://www.flamingspork.com/blog/2013/03/05/mysql-code-size/ https://www.flamingspork.com/blog/2013/03/05/mysql-code-size... Edit: See also this interview with Percona's CEO - http://www.zdnet.com/article/mysql-why-the-open-source-database-is-better-off-under-oracle/ http://www.zdnet.com/article/mysql-why-the-open-source-datab...
- jordigh 12y ago
  And I unlazied myself a little and found this: https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-features/ https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-features/ If marketing is to be believed, it does seem like MariaDB offers many points of attraction over MySQL. The fact that Oracle does not provide test cases or has proprietary extensions is a bit alarming from a software freedom perspective.

jkoudys 12y ago

> The main effort of the team has been focused on speed, with performance reportedly improved from 2 to 3 times compared to previous releases. Definitely good news, as MySQL came out during the peak of Moore's-law (or, more appropriately, a misapplication of) fueled idiocy where nobody seemed interested in investing in better performing software, since they all expected they'd have faster hardware next year. Now everybody's deploying to VPSes, so it's once again important that we get the most out of every single CPU cycle. I haven't gone through all the diffs, but if they're promising 2x to 3x improved performance, there must have been some pretty fundamental rewrites of old code. Coming from the Oracle + DB2 world, what I'd really like to see is some improved performance analysis and query optimization tools. There have been some incremental improvements to EXPLAIN (the new 'EXPLAIN on a named connection' feature seems pretty cool for when I have 10+ application instances all connecting to my DB), but it's still got a long way to go.

morgo 12y ago
I totally hear you here :) Visibility is the most useful and always under-rated feature. If I can clarify some of the recent enhancements here: - MySQL 5.6 introduced `EXPLAIN FORMAT=JSON`. MySQL Workbench uses this to visualize query plans (important as they get complicated.) - Also in 5.6 was optimizer trace (find out why indexes were not used etc.) and performance_schema enabled by default. - MySQL 5.7 adds cost information to `EXPLAIN FORMAT=JSON` (Workbench also understands it.) - Workbench also has a set of performance views based on Performance_schema (based on a project called SYS). You can install it as standalone from here too: https://github.com/MarkLeith/mysql-sys https://github.com/MarkLeith/mysql-sys - The runtime performance data from SYS is very useful for making correct optimization decisions. Being an SQL interface is also friendly for writing your own scripts against it. Also, to clarify on your first paragraph: Yes, refactoring old code was one of the ways this was achieved. We picked refactoring targets based on performance and because some of the older code is not very testable.

dschiptsov 12y ago

multiple page cleaner threads - this is nice.

deleted 12y ago

[deleted]