- Server might refuse to start, asking users to manually run mariadb-upgrade
Can you describe this one more, mariadb-upgrade requires the server started which is the point of this request to fix.
This is a very popular one on Stack Overflow: https://stackoverflow.com/questions/27918764/cannot-load-from-mysql-proc-the... When users see the server failing to start and logs contain the very scary error message "mysql.proc corrupted". Some users might recover their entire database from backups as they think it was corrupted - but real fix is to simply run mariadb-upgrade which will update the system tables and the numer of columns/names in mysql.proc will match what the new mariadbd binary expects and then it will run just fine. But this is just one example in a long list of scenarios where users suffer - all of them would go away if mariadbd itself did it's own upgrade without relying on any external admin or system to run a separate mariadb-upgrade script. ..
Can we please have this?
Can we agree that this would be a desired feature in next MariaDB 11.x version, and if somebody implements this, it would be timely reviewed and merged?
There is already design outlined at https://jira.mariadb.org/browse/MDEV-30499
Thanks for showing the other use cases Otto.
You are welcome! Looking forward and hoping this one will get traction.