[debian-mysql] Discussion on handling 5.6 related matters
otto at seravo.fi
Wed Jul 9 11:52:03 UTC 2014
2014-07-08 20:04 GMT+03:00 Robie Basak <robie.basak at canonical.com>:
>> 1. Fresh start with blank data dir.
>> 1. Uninstall MySQL 5.x as regular removal.
> We want co-installability though, right? So removal would no longer be
I don't think we need co-installability, as admins are likely to pick
just on variant and then run it..? Only one kind of server can listen
at port 3306 per server The only case where co-installation is perhaps
needed, is to be able to run a database dump from one
binary-incompatible format to import to another server due to
I think the primary motivation here is to make installation safer and
with separation of data dir, admins are less likely to accidentally
"reformat" their database files binary format into a new version that
inhibits reverting back to old server version. But that would indeed
require that the data files are copied to a new datadir, and not
renamed. And I don't think we can assume that all servers have enough
disk space to have duplicate db data?
What if we just put a big bold warning in the installer that
installing package X will do a possibly one-way migration for the data
files? Or install new servers with empty databases and notify the user
they need to run either cp X Y or mv X Y to copy or migrate the data?
Check out our blog at http://seravo.fi/blog
and follow @ottokekalainen
More information about the pkg-mysql-maint