Oracle MySQL 8.0 GA Stable Release

eva2000 · May 3, 2018

Important issue with MySQL 8.0 on initial release that is overlooked is whether or not 3rd party backup tools support the MySQL 8.0 changes a critical piece is missing for Oracle MySQL 8 (GA) … « Serge Frezefond 's blog

Oracle MySQL 8.0 has been declared GA but a critical piece is missing …
MySQL 8 is a fantastic release embedding the work of brilliant Oracle engineering.
I will not detail all the great features of MySQL 8 as there are a lot of great presentations around it. What’s New in MySQL 8.0? (Generally Available)

One of my main concern regarding MySQL 8 is that it comes without an online backup solution. You only have access to online backup through MySQL Enterprise Backup that you get with a MySQL Enterprise Edition subscription. This is 5000 USD per server per year.So if you have 20 servers for 10 years usage of online backup you will give 1 million $ to Oracle

Of course at some point there might be a third party online backup solution available for MySQL 8. But writing this piece of code is tricky as MySQL 8 has introduced major design changes : disk format, innoDB data dictionary … Another practical problem is that MySQL is designed, developed and debugged behind closed doors. The third party cannot expect much help from Oracle to develop and fix its backup solution. The third party online backup solution can break following any upstream change done by Oracle. And I imagine that bugs in this area can be quite tricky to detect and fix without access to Oracle engineering !

Imagine the online backup bug happens after a security fix you have to apply to be compliant. You have the dilemma : being compliant but loosing online backup capability or being uncompliant and having online backup. The third solution is of course to pay Oracle to have access to closed source MySQL Enterprise which includes MySQL Backup.

MariaDB comes with a solution by having a bundled online backup solution on which it has full control and that does not depend on MySQL upstream code. This is the benefit for MariaDB to be a true fork ;-)
Click to expand...

eva2000 · May 3, 2018

MariaDB and MySQL creator Monty takes MySQL 8.0 for a spin and compares it to MariaDB 10.3 for single threaded tests Monty says: Congratulations to Oracle on MySQL 8.0

I did run the test both with MySQL 8.0 and MariaDB 10.3 with the InnoDB storage engine and by having identical values for all InnoDB variables, table-definition-cache and table-open-cache. I turned off performance schema for both databases. All test are run with a user with an empty password (to keep things comparable and because it's was too complex to generate a password in MySQL 8.0)
Click to expand...

Results are in seconds to complete
Code (Text):
Operation         |MariaDB|MySQL-8|

-----------------------------------
ATIS              | 153.00| 228.00|
alter-table       |  92.00| 792.00|
big-tables        | 990.00|2079.00|
connect           | 186.00| 227.00|
create            | 575.00|4465.00|
insert            |4552.00|8458.00|
select            | 333.00| 412.00|
table-elimination |1900.00|3916.00|
wisconsin         | 272.00| 590.00|
-----------------------------------
This is of course just a first view of the performance of MySQL 8.0 in a single user environment. Some reflections about the results:

Alter-table test is slower (as expected) in 8.0 as some of the alter tests benefits of the instant add column in MariaDB 10.3.

connect test is also better for MariaDB as we put a lot of efforts to speed this up in MariaDB 10.2

table-elimination shows an optimization in MariaDB for the Anchor table model, which MySQL doesn't have.

CREATE and DROP TABLE is almost 8 times slower in MySQL 8.0 than in MariaDB 10.3. I assume this is the cost of 'atomic DDL'. This may also cause performance problems for any thread using the data dictionary when another thread is creating/dropping tables.

When looking at the individual test results, MySQL 8.0 was slower in almost every test, in many significantly slower.

The only test where MySQL was faster was "update_with_key_prefix". I checked this and noticed that there was a bug in the test and the columns was updated to it's original value (which should be instant with any storage engine). This is an old bug that MySQL has found and fixed and that we have not been aware of in the test or in MariaDB.

While writing this, I noticed that MySQL 8.0 is now using utf8mb4 as the default character set instead of latin1. This may affect some of the benchmarks slightly (not much as most tests works with numbers and Oracle claims that utf8mb4 is only 20% slower than latin1), but needs to be verified.

Oracle claims that MySQL 8.0 is much faster on multi user benchmarks. The above test indicates that they may have done this by sacrificing single user performance.

We need to do more and many different benchmarks to better understand exactly what is going on. Stay tuned!

Click to expand...

Short summary of my first run with MySQL 8.0:

Using the new caching_sha2_password authentication as default for new installation is likely to cause a lot of problems for users. No old application will be able to use MySQL 8.0, installed with default options, without moving to MySQL's client libraries. While working on this blog I saw MySQL users complain on IRC that not even MySQL Workbench can authenticate with MySQL 8.0. This is the first time in MySQL's history where such an incompatible change has ever been done!

Atomic DDL is a good thing (We plan to have this in MariaDB 10.4), but it should not have such a drastic impact on performance. I am also a bit skeptical of MySQL 8.0 having just one copy of the data dictionary as if this gets corrupted you will lose all your data. (Single point of failure)

MySQL 8.0 has several new reserved words and hasremoved a lot of variables, which makes upgrades hard. Before upgrading to MySQL 8.0 one has to check all one's databases and applications to ensure that there are no conflicts.

As my test above shows, if you have a single deprecated variable in your configuration files, the installation of MySQL will abort and can leave the database in inconsistent state. I did of course my tests by installing into an empty data dictionary, but one can assume that some of the problems may also happen when upgrading an old installation.

Click to expand...

With that said looking forward to playing with MariaDB 10.2/10.3 more in future to compare with MySQL 8.0

eva2000 · May 3, 2018

regarding

Using the new caching_sha2_password authentication as default for new installation is likely to cause a lot of problems for users. No old application will be able to use MySQL 8.0, installed with default options, without moving to MySQL's client libraries. While working on this blog I saw MySQL users complain on IRC that not even MySQL Workbench can authenticate with MySQL 8.0. This is the first time in MySQL's history where such an incompatible change has ever been done!

Click to expand...

Upgrading to MySQL 8.0 : Default Authentication Plugin Considerations
If you are upgrading your server to MySQL 8.0 and observe that your application is experiencing error related caching_sha2_password plugin, it is likely because your clients/connectors does not (yet) support caching_sha2_password plugin. To resolve this issue, you may consider using mysql_native_password as default authentication for MySQL 8.0 server. Add following entry in MySQL configuration file.
Code (Text):
[mysqld]
default-authentication-plugin=mysql_native_password
This way, once server is restarted, your existing applications should be able to connect to the server without any issues.

Here is the list of connectors that have caching_sha2_password support.

At the time of writing this post, following connectors do not have support for caching_sha2_password.

PHP mysqli connector

GO mysql connector

PERL DBD-mysql connector

Please note that this list is not exhaustive.

Let us know if you still have problems after the upgrade.

However, you should actively consider to switch to caching_sha2_password as the default choice for authentication (and authentication plugin for your existing user accounts) because it provides better security. So, check with your Connector provider for updates on the support for caching_sha2_password.
Click to expand...
and MySQL :: MySQL 8.0 Reference Manual :: 2.10.1.2 Changes Affecting Upgrades to MySQL 8.0

caching_sha2_password as the Preferred Authentication Plugin
The caching_sha2_password and sha256_password authentication plugins provide more secure password encryption than the mysql_native_passwordplugin, and caching_sha2_password provides better performance than sha256_password. Due to these superior security and performance characteristics ofcaching_sha2_password, it is as of MySQL 8.0.4 the preferred authentication plugin, and is also the default authentication plugin rather thanmysql_native_password. This change affects both the server and the libmysqlclient client library:
Click to expand...

caching_sha2_password-Compatible Clients and Connectors
If a client or connector is available that has been updated to know about caching_sha2_password, using it is the best way to ensure compatibility when connecting to a MySQL 8.0 server configured with caching_sha2_password as the default authentication plugin.

These clients and connectors have been upgraded to support caching_sha2_password:

The libmysqlclient client library in MySQL 8.0.4 or higher. Standard MySQL clients such as mysql and mysqladmin are libmysqlclient-based, so they are compatible as well.

MySQL Connector/C++ 1.1.11 or higher or 8.0.7 or higher.

MySQL Connector/J 8.0.9 or higher.

MySQL Connector/Net 8.0.10 or higher (through the classic MySQL protocol).

MySQL Connector/Node.js 8.0.9 or higher.

PHP: the X DevAPI PHP extension (mysql_xdevapi) supports it.

PHP: the PDO_MySQL and ext/mysqli extensions do not. In addition, when used with PHP versions before 7.1.16 and PHP 7.2 before 7.2.4, they fail to connect with default_authentication_plugin=caching_sha2_password even if caching_sha2_password is not used.

Click to expand...

Clients that use an implementation of the client/server protocol other than libmysqlclient may need to be upgraded to a newer version that understands the new authentication plugin. For example, in PHP, MySQL connectivity usually is based on mysqlnd, which currently does not know aboutcaching_sha2_password. Until an updated version of mysqlnd is available, the way to enable PHP clients to connect to MySQL 8.0 is to reconfigure the server to revert to mysql_native_password as the default authentication plugin, as previously discussed.
Click to expand...

eva2000 · May 27, 2018

More testing for Oracle MySQL 8.0 on Centmin Mod 123.09beta01. I setup custom mysql-control command to manage multiple MySQL server instances more easily. For example, I setup 2x MariaDB 10.1 MySQL instances + Oracle MySQL 8.0.11 all on the same server with separate MySQL sockets, listening ports and MySQL data directories so can test various MySQL configurations to learn and compare MySQL 8.0 vs MariaDB 10.1

Code (Text):

mysql-control

Usage:

mysql-control 1 mysqladmin ver
mysql-control 2 mysqladmin ver
mysql-control 3 mysqladmin ver
mysql-control 8 mysqladmin ver

mysql-control 1 show-engines
mysql-control 2 show-engines
mysql-control 3 show-engines
mysql-control 8 show-engines

mysql-control Main MariaDB 10.1

Code (Text):

/usr/bin/mysql-control 1 mysqladmin ver
mysqladmin -P 3306 -S /var/lib/mysql/mysql.sock ver  
mysqladmin  Ver 9.1 Distrib 10.1.32-MariaDB, for Linux on x86_64
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Server version          10.1.32-MariaDB
Protocol version        10
Connection              Localhost via UNIX socket
UNIX socket             /var/lib/mysql/mysql.sock
Uptime:                 1 hour 6 min 44 sec

Threads: 1  Questions: 18  Slow queries: 0  Opens: 17  Flush tables: 1  Open tables: 11  Queries per second avg: 0.004

Code (Text):

/usr/bin/mysql-control 1 show-engines
mysql -P 3306 -S /var/lib/mysql/mysql.sock -e "SHOW ENGINES;"
+--------------------+---------+--------------------------------------------------------------------------------------------------+--------------+------+------------+
| Engine             | Support | Comment                                                                                          | Transactions | XA   | Savepoints |
+--------------------+---------+--------------------------------------------------------------------------------------------------+--------------+------+------------+
| CSV                | YES     | CSV storage engine                                                                               | NO           | NO   | NO         |
| MRG_MyISAM         | YES     | Collection of identical MyISAM tables                                                            | NO           | NO   | NO         |
| MyISAM             | YES     | MyISAM storage engine                                                                            | NO           | NO   | NO         |
| SEQUENCE           | YES     | Generated tables filled with sequential values                                                   | YES          | NO   | YES        |
| MEMORY             | YES     | Hash based, stored in memory, useful for temporary tables                                        | NO           | NO   | NO         |
| PERFORMANCE_SCHEMA | YES     | Performance Schema                                                                               | NO           | NO   | NO         |
| Aria               | YES     | Crash-safe tables with MyISAM heritage                                                           | NO           | NO   | NO         |
| InnoDB             | DEFAULT | Percona-XtraDB, Supports transactions, row-level locking, foreign keys and encryption for tables | YES          | YES  | YES        |
+--------------------+---------+--------------------------------------------------------------------------------------------------+--------------+------+------------+

mysql-control Second MariaDB 10.1

Code (Text):

/usr/bin/mysql-control 2 mysqladmin ver
mysqladmin -P 3307 -S /var/lib/mysql2/mysql.sock ver  
mysqladmin  Ver 9.1 Distrib 10.1.32-MariaDB, for Linux on x86_64
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Server version          10.1.32-MariaDB
Protocol version        10
Connection              Localhost via UNIX socket
UNIX socket             /var/lib/mysql2/mysql.sock
Uptime:                 53 min 27 sec

Threads: 1  Questions: 5  Slow queries: 0  Opens: 17  Flush tables: 1  Open tables: 11  Queries per second avg: 0.001

Code (Text):

/usr/bin/mysql-control 2 show-engines
mysql -P 3307 -S /var/lib/mysql2/mysql.sock -e "SHOW ENGINES;"
+--------------------+---------+--------------------------------------------------------------------------------------------------+--------------+------+------------+
| Engine             | Support | Comment                                                                                          | Transactions | XA   | Savepoints |
+--------------------+---------+--------------------------------------------------------------------------------------------------+--------------+------+------------+
| CSV                | YES     | CSV storage engine                                                                               | NO           | NO   | NO         |
| MRG_MyISAM         | YES     | Collection of identical MyISAM tables                                                            | NO           | NO   | NO         |
| MyISAM             | YES     | MyISAM storage engine                                                                            | NO           | NO   | NO         |
| SEQUENCE           | YES     | Generated tables filled with sequential values                                                   | YES          | NO   | YES        |
| MEMORY             | YES     | Hash based, stored in memory, useful for temporary tables                                        | NO           | NO   | NO         |
| PERFORMANCE_SCHEMA | YES     | Performance Schema                                                                               | NO           | NO   | NO         |
| Aria               | YES     | Crash-safe tables with MyISAM heritage                                                           | NO           | NO   | NO         |
| InnoDB             | DEFAULT | Percona-XtraDB, Supports transactions, row-level locking, foreign keys and encryption for tables | YES          | YES  | YES        |
+--------------------+---------+--------------------------------------------------------------------------------------------------+--------------+------+------------+

mysql-control Oracle MySQL 8.0

Code (Text):

/usr/bin/mysql-control 8 mysqladmin ver 
/usr/local/mysql/bin/mysqladmin -P 3407 -S /opt/mysql/data/mysql.sock ver   
/usr/local/mysql/bin/mysqladmin  Ver 8.0.11 for el7 on x86_64 (MySQL Community Server - GPL)
Copyright (c) 2000, 2018, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Server version          8.0.11
Protocol version        10
Connection              Localhost via UNIX socket
UNIX socket             /opt/mysql/data/mysql.sock
Uptime:                 1 hour 44 min 44 sec

Threads: 2  Questions: 10  Slow queries: 0  Opens: 110  Flush tables: 2  Open tables: 86  Queries per second avg: 0.001

Code (Text):

/usr/bin/mysql-control 8 show-engines
mysql -P 3407 -S /opt/mysql/data/mysql.sock -e "SHOW ENGINES;"
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
| Engine             | Support | Comment                                                        | Transactions | XA   | Savepoints |
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
| FEDERATED          | NO      | Federated MySQL storage engine                                 | NULL         | NULL | NULL       |
| MEMORY             | YES     | Hash based, stored in memory, useful for temporary tables      | NO           | NO   | NO         |
| InnoDB             | DEFAULT | Supports transactions, row-level locking, and foreign keys     | YES          | YES  | YES        |
| PERFORMANCE_SCHEMA | YES     | Performance Schema                                             | NO           | NO   | NO         |
| MyISAM             | YES     | MyISAM storage engine                                          | NO           | NO   | NO         |
| MRG_MYISAM         | YES     | Collection of identical MyISAM tables                          | NO           | NO   | NO         |
| BLACKHOLE          | YES     | /dev/null storage engine (anything you write to it disappears) | NO           | NO   | NO         |
| CSV                | YES     | CSV storage engine                                             | NO           | NO   | NO         |
| ARCHIVE            | YES     | Archive storage engine                                         | NO           | NO   | NO         |
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+

Vijay Singh Khatri · Jan 4, 2019

It's really awesome news for those who are using a MySQL database. Get the difference between MySQL and MariaDB from here.

Revenge · Jan 4, 2019

Vijay Singh Khatri said: ↑

It's really awesome news for those who are using a MySQL database. Get the difference between MySQL and MariaDB from here.
Click to expand...

Compatibility
MariaDB team is making sure that MariaDB can seamlessly replace MySQL in the existing applications. In fact, for each version of MySQL, they release the same version number of MariaDB to indicate that MariaDB is generally compatible with the corresponding MySQL version. This opens up the possibility of switching to MariaDB seamlessly without any modifications in the application code-base.
Click to expand...

What?

eva2000 · Jul 16, 2019

Revenge said: ↑

What?
Click to expand...

Yeah they no longer do that MariaDB version numbers have long since differed from Oracle MySQL nowadays

tininho · Jul 17, 2019

I am more than eager to test out MySQL8 on Centminmod, but I can't/don't know how to install it myself. Is it possible to test this somehow (I could not figure it out from this topic) or should I just wait patiently?

Looking for performance in WP All Import Woocommerce import jobs.

eva2000 · Jul 17, 2019

Unfortunately, no automated way for using MySQL 8 on Centmin Mod as yet. If you're unfamiliar with MySQL 8 I'd wait as their are drastic changes which can break existing web app's usage for reasons outlined in this thread.

Unfortunately, no time to test MySQL 8 any further as I have been alot busier on my end with cPanel's latest price increases and after effects i.e. cPanel clients migrating to DirectAdmin and/or Centmin Mod - writing cPanel to Centmin Mod importer for some of my paying clients and having to learn DirectAdmin and writing up documentation for such for my own records

Revenge · Jul 31, 2019

In the last version 8.0.17, MEMBER is now a reserved word. This can cause issues, at least with IPS because they have columns named MEMBER. (IPS is going to release a patch because of this)

This seems to me a very big change for a small version release.

https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-17.html#mysqld-8-0-17-feature

steph40 · Jul 31, 2019

Wow, why would they do that?

eva2000 · Jul 31, 2019

Revenge said: ↑

In the last version 8.0.17, MEMBER is now a reserved word. This can cause issues, at least with IPS because they have columns named MEMBER. (IPS is going to release a patch because of this)

This seems to me a very big change for a small version release.

https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-17.html#mysqld-8-0-17-feature
Click to expand...

ouch that can potentially mess with alot of folks !!

eva2000 · Oct 29, 2019

Had a paying client hire me to switch their Centmin Mod 123.09beta01 installs from MariaDB 10.3 to MySQL 8.0 server due to their web app usage requirements. So had some quality time working with MySQL 8.0 on Centmin Mod

MySQL 8 support is on Centmin Mod's long term To-Do/Wishlist outlined here

But won't be available to general public anytime soon due to work and testing needed for automatic tuning and optimisation formulas for /etc/my.cnf settings based on detected server cpu, memory, disk resources. Lots of different and new MySQL 8 variables and settings to play with

My tests on local VirtualBox CentOS 7 server with Centmin Mod 123.09beta01

Code (Text):

cat /etc/redhat-release ; cat /etc/centminmod-release
CentOS Linux release 7.7.1908 (Core)
123.09beta01.b301

Code (Text):

mysqladmin ver
mysqladmin  Ver 8.0.18 for Linux on x86_64 (MySQL Community Server - GPL)
Copyright (c) 2000, 2019, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Server version          8.0.18
Protocol version        10
Connection              Localhost via UNIX socket
UNIX socket             /var/lib/mysql/mysql.sock
Uptime:                 17 min 55 sec
Threads: 2  Questions: 7  Slow queries: 0  Opens: 132  Flush tables: 3  Open tables: 52  Queries per second avg: 0.006

Code (Text):

yum -q list mysql-community-client mysql-community-server mysql-community-libs-compat mysql-community-devel mysql-community-common --disableexcludes=main
Installed                           Packages
mysql-community-client.x86_64       8.0.18-1.el7  @mysql80-community
mysql-community-common.x86_64       8.0.18-1.el7  @mysql80-community
mysql-community-devel.x86_64        8.0.18-1.el7  @mysql80-community
mysql-community-libs-compat.x86_64  8.0.18-1.el7  @mysql80-community
mysql-community-server.x86_64       8.0.18-1.el7  @mysql80-community
Available                           Packages
mysql-community-client.i686         8.0.18-1.el7  mysql80-community
mysql-community-common.i686         8.0.18-1.el7  mysql80-community
mysql-community-devel.i686          8.0.18-1.el7  mysql80-community
mysql-community-libs-compat.i686    8.0.18-1.el7  mysql80-community

Centmin Mod command shortcuts

Code (Text):

mysqlstatus
Redirecting to /bin/systemctl status mysqld.service
● mysqld.service - MySQL Server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; disabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/mysqld.service.d
           └─limits.conf
   Active: active (running) since Mon 2019-10-28 15:47:27 UTC; 17min ago
     Docs: man:mysqld(8)
           http://dev.mysql.com/doc/refman/en/using-systemd.html
 Main PID: 28644 (mysqld)
   Status: "Server is operational"
   CGroup: /system.slice/mysqld.service
           └─28644 /usr/sbin/mysqld
Oct 28 15:47:21 centos7.localdomain systemd[1]: Stopped MySQL Server.
Oct 28 15:47:21 centos7.localdomain systemd[1]: Starting MySQL Server...
Oct 28 15:47:27 centos7.localdomain systemd[1]: Started MySQL Server.

eva2000 · Jan 11, 2020

So apparently looks like MySQL 8's minor version upgrades are one way only and can not be downgraded MySQL 8 Minor Version Upgrades Are ONE-WAY Only - Percona Database Performance Blog ! So with MySQL 8 from Oracle or Percona, even minor version upgrades require a full mysql database backup for all databases on the server !

In the many years we have used MySQL, we got accustomed to the fact that upgrades from MySQL 5.7.11 to 5.7.12 was a minor event. This meant that if something was going wrong, we could roll back the binaries and be happy again.

From MySQL 8, this is no longer true. Any upgrade, even minor, is seen as irreversible. (This is valid for Percona Server for MySQL as well.)
Click to expand...

This is clearly stated in the MySQL documentation. You may not like it, but that is how it is now.

Here are some things to think about. Upgrading a minor MySQL version in the past was a trivial activity, and very often automation was doing that silently. That was not the best practice but it was the reality. At the same time, testing was very often superficial, if done at all.

That attitude must change.

You CANNOT do an upgrade to a MINOR VERSION without:

Full Backup/restore testing (backup must be a logical one, like: mysqldump or mydumper or any other tool that allow you to export the data)

Severe functional/application testing IN A STAGING environment

You should disable ANY automation that performs silent/untested upgrade in production

Also keep in mind that IF you take a backup, if you have terabytes or even maybe just a GB of data, the rollback will not be immediate at all.

Given that, you should:

Plan carefully, use a proper platform for the tests (like a full populated staging).

Use as much real load as possible from your application.

Upgrade from the last server of the slave chain up.

Do not rush trying to catch/implement the latest shiny feature.

One last but NOT SUPPORTED approach (see documentation), is to rely on replication as described in Replicating from MySQL 8.0 to MySQL 5.7. But remember, this is done at your own risk, given it is not fully supported by MySQL/Oracle.

These are the minimal steps needed to perform minor version upgrades and to be safe. Great MySQL to everybody!
Click to expand...

BamaStangGuy · Jan 11, 2020

Saw this coming from a mile away and so did MariaDB. Oracle can suck it. Percona is the one left screwed now by sticking down the same line. Their support team is going to have fun with this.

pamamolf · Jan 11, 2020

Mysql 8 shouldn't compared with Mariadb 10.4 ?

eva2000 · Jan 12, 2020

BamaStangGuy said: ↑

Saw this coming from a mile away and so did MariaDB. Oracle can suck it. Percona is the one left screwed now by sticking down the same line. Their support team is going to have fun with this.
Click to expand...

Yeah it's a pretty big gotcha for folks unaware. Imagine all the other control panels out their offering MySQL 8 support as well ! But then question is how many folks usually run a downgrade of MySQL minor versions ? But then even if folks did do backups, most folks only backup their own databases and not ones from the system i.e. database named = mysql etc. So that's downtime if they downgrade MySQL 8 and forget to backup the system databases too.

Also imagine the amout of extra database related backup disk storage required if you now need to backup prior to each MySQL 8 minor version upgrade !

Looks like for MySQL 8, you want to have more control over minor/major upgrade routines and maybe implement a version lock (YUM) to prevent automated MySQL 8 minor version updates and then script a full all databases on server backup + yum version unlock + mysql yum upgrade type routine. For the MariaDB to Oracle MySQL 8 auto switch script I wrote for Centmin Mod I am testing for a paying client, I am going to add the yum version unlock and add scripted approach to MySQL 8 YUM upgrades.

pamamolf said: ↑

Mysql 8 shouldn't compared with Mariadb 10.4 ?
Click to expand...

BamaStangGuy said: ↑

Saw this coming from a mile away and so did MariaDB. Oracle can suck it. Percona is the one left screwed now by sticking down the same line. Their support team is going to have fun with this.
Click to expand...

pamamolf said: ↑

Mysql 8 shouldn't compared with Mariadb 10.4 ?
Click to expand...

Totally different with how MariaDB 10.4 changed https://community.centminmod.com/threads/interesting-look-at-whats-new-in-mariadb-10-4.17676/. Long term right now, I'd stick with MariaDB 10.3 or MySQL 5.7 if you need to be able to switch between MySQL versions from MariaDB, Oracle and Percona. If you use MySQL 8.0, don't expect to be able to easily switch to MariaDB 10.4 and vice versa without a full backup and restore and cross your fingers.

And there's general differences too https://community.centminmod.com/threads/mariadb-mysql-vs-oracle-mysql-vs-percona-mysql.13853/

buik · Jan 12, 2020

Hihi 4 pages for one lousy MySQL release, do not make me laugh

I really don't understand the problem at all.
If you really want to make speed gains you will have to break with the code past.
Compatibility code is always difficult.

It is clear in advance what the conditions are.

If you don't want this, it's fine too.
As long as there are sufficient alternatives.
And there are lots of alternatives.

Next!

eva2000 · Jan 14, 2020

buik said: ↑

Hihi 4 pages for one lousy MySQL release, do not make me laugh

I really don't understand the problem at all.
If you really want to make speed gains you will have to break with the code past.
Compatibility code is always difficult.

It is clear in advance what the conditions are.

If you don't want this, it's fine too.
As long as there are sufficient alternatives.
And there are lots of alternatives.

Next!
Click to expand...

MySQL 8 is an exciting release hence the amount of discussions. Though the drastic changes for performance will bring along of gotchas if you don't read all the documentation. Hence, why I have only been testing MySQL 8 in non-production environments to ensure my level of know-how is adequate. This insight regarding minor version rollbacks is just another tidbit of info to add to my knowledge bank

Yes so that's why I stick with MariaDB 10.3 for now - MariaDB 10.4 like MySQL 8.0 have more drastic changes too.

Log in / Register

Forums

Learn about Centmin Mod LEMP Stack today

Oracle MySQL 8.0 GA Stable Release

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

Vijay Singh Khatri New Member

Revenge Active Member

eva2000 Administrator Staff Member

tininho Active Member

eva2000 Administrator Staff Member

Revenge Active Member

steph40 Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

BamaStangGuy Active Member

pamamolf Premium Member Premium Member

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

.

Log in / Register

Useful Searches

Learn about Centmin Mod LEMP Stack today

Oracle MySQL 8.0 GA Stable Release

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

Vijay Singh Khatri New Member

Revenge Active Member

eva2000 Administrator Staff Member

tininho Active Member

eva2000 Administrator Staff Member

Revenge Active Member

steph40 Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

eva2000 Administrator Staff Member

BamaStangGuy Active Member

pamamolf Premium Member Premium Member

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

.