MySQL 8.2 Release Notes
Notes
Make sure you understand the release model for MySQL innovation and long-term support (LTS) versions before you proceed with a downgrade.
Monthly Rapid Updates (MRUs) and hotfixes also count as "releases" in the following discussions.
We use "8.4.x LTS" as an example for an LTS release and "8.3.0" as an example for a bugfix release only for illustrative purposes.
The supported downgrade paths for MySQL Server are listed in Table 2.15, “Downgrade Paths for MySQL Server” below:
Table 2.15 Downgrade Paths for MySQL Server
| Downgrade Path | Path Examples | Downgrade Methods | Notes |
|---|---|---|---|
| Within an LTS or bugfix release series | 8.0.36 to 8.0.35 8.4.x+1 LTS to 8.4.x LTS |
in-place downgrade, logical downgrade, asynchronous replication, MySQL Clone | In-place downgrade to 8.0.34 is not supported. |
| From an LTS or bugfix release to the last LTS or bugfix release series | 8.4.x LTS to 8.0.y | logical downgrade, asynchronous replication | Only supported for rollback purposes (that is, if no new server functionality has been applied to the data) |
| From an LTS or bugfix release to an innovation release after the last LTS series | 8.4.x LTS to 8.3.0 | logical downgrade, asynchronous replication | Only supported for rollback purposes (that is, if no new server functionality has been applied to the data) |
| From an innovation release series to another one after the last LTS series | 8.2 to 8.1 | logical downgrade, asynchronous replication | Only supported for rollback purposes (that is, if no new server functionality has been applied to the data) |
Downgrading to MySQL 5.7 or earlier is not supported.