Check out VARIABLES for aria_block_size . Its existence almost certainly implies some version of MariaDB, not MySQL, as well as Percona. (At least in the near future.)
Initial version :
- "5.7" and "8.0" Suppose MySQL or Percona; it will not mean MariaDB.
- "10.2" implies MariaDB; MySQL and Percona are unlikely to be at "10" for a long time.
What function do you need? There is a possibility that Percona will modify something from MariaDB 10.2 before it comes from MySQL.
Even when version is 5.1.53-rel11.7-log or 5.5.35-0ubuntu0.12.04.2-log , the first part gives you an important part of the MySQL / MariaDB / Percona version.
Percona versions look like this: 5.5.31-30.3-log , 5.6.30-76.3-56-log , 5.6.19-67.0-log - Pay attention to the additional 2 or 3 numbers after the initial 3.
MariaDB always starts with NNN-MariaDB
Oracle MySQL starts with NNN , but can continue with -enterprise (paid version), -community (free version), -0ubuntu0 (ported to Ubuntu), -Debian , etc.
MariaDB: 5.1, 5.2, 5.3, 5.4, 5.5, 10.0, 10.1, 10.2
Oracle and Percona: 5.1, 5.5, 5.6, 5.7, 8.0
Cycle 8.0 is just beginning. This means that 5.6 will close soon, and 5.7 has some kind of life left, but it will not have much new.
An explanation of what is the "main" release.
For MySQL (and Percona) they are "core" and they are not sequential ': 5.1, 5.5, 5.6, 5.7, 8.0.
For MariaDB: 5.1, 5.2, 5.3, 5.4, 5.5, 10.0, 10.1, 10.2.