Bug #95216 Improve clarity of downgrade documentation
Submitted: 1 May 2019 21:13 Modified: 10 May 2019 16:12
Reporter: Ceri Williams Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:8.0 OS:Any
Assigned to: CPU Architecture:Any
Tags: bug#27708249, downgrade, MY-013171

[1 May 2019 21:13] Ceri Williams
Description:
The server documentation contains a information page regarding downgrades: https://dev.mysql.com/doc/refman/8.0/en/downgrading.html

Whilst it is easy to notice that, unlike previous versions (e.g. https://dev.mysql.com/doc/refman/5.7/en/downgrading.html), there are no links through to further details , is is not blatant that downgrades are simply NOT POSSIBLE AT ALL

A note states:

"Downgrade from MySQL 8.0 to MySQL 5.7 (or from a MySQL 8.0 release to a previous MySQL 8.0 release) is not supported. The only supported alternative is to restore a backup taken before upgrading. It is therefore imperative that you backup your data before starting the upgrade process."

If you scan that it is easy enough to miss a rather important piece of information: "or from a MySQL 8.0 release to a previous MySQL 8.0 release"

This is not the kind of thing to be subtle about as nobody wants to find out that they have to rollback and then hit an issue where MySQL aborts on boot.

How to repeat:
N/A

Suggested fix:
Remove the irrelevant content that appears to be share across pages and either make the note the main content or state something along the lines of "Downgrades, including to a previous MySQL 8.0 minor version are not possible"

If the intention is to resolve the problem of MySQL 8.0 being unable to run minor version downgrades then perhaps the documentation should instead explicitly reflect that until such a time that it becomes possible.
[2 May 2019 4:30] MySQL Verification Team
Hello Ceri Williams!

Thank you for the report!

Thanks,
Umesh
[10 May 2019 16:12] Daniel Price
Posted by developer:
 
The referenced documentation was updated. The changes should appear online soon.

Thank you for the bug report.