This morning, this Percona XtraBackup bug came to my attention:Â https://bugs.launchpad.net/bugs/1170340Â – basically, it’s now really quite tricky to determine if a MySQL server you’re connected to supports partitioning or not.
If you’re connected to anything less than MySQL 5.6, you can use have_partitioning variable. But since that’s gone in 5.6, you’re going to get a false negative if you’re connected to 5.6. You could use INFORMATION_SCHEMA.PLUGINS table, but that’s not there in 5.0, so you have some added workarounds to add there too.
A simple version check could be the solution… but what if you compiled the server without partitioning support?
ya it’s another typical example of stupid cleanups.
We had this with TYPE= vs ENGINE= for years, and at least that was a parser token that could actually save time/space when removed.
Detecting if a MySQL server supports partitioning: This morning, this Percona XtraBackup bug came to my attent… http://t.co/GnbRg8fpfv
New #mysql planet post : Detecting if a MySQL server supports partitioning http://t.co/ct8xcxMziP
Aleksandr Kuzminsky liked this on Facebook.
It supports partitioning. Nobody compiles without it.
Valerii Kravchuk liked this on Facebook.