On 25.11.2021 04:21, Thomas Deutschmann wrote: > Bug: https://bugs.gentoo.org/825234 > Signed-off-by: Thomas Deutschmann <whi...@gentoo.org> > --- > ...adb-database-restore-maybe-required.en.txt | 46 +++++++++++++++++++ > 1 file changed, 46 insertions(+) > create mode 100644 > 2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt > > diff --git > a/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt > > b/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt > new file mode 100644 > index 0000000..c4a698e > --- /dev/null > +++ > b/2021-11-23-mariadb-database-restore-maybe-required/2021-11-23-mariadb-database-restore-maybe-required.en.txt > @@ -0,0 +1,46 @@ > +Title: Full MariaDB database restore maybe required > +Author: Thomas Deutschmann <whi...@gentoo.org> > +Posted: 2021-11-23 > +Revision: 1 > +News-Item-Format: 2.0 > +Display-If-Installed: dev-db/mariadb > +Display-If-Installed: sys-cluster/galera > + > +On 2021-11-21, a member of the QA project accidentially de-keyworded Agreed with others in the thread, this is not professional.
> +MariaDB 10.6 to address a file collision, users, who also had latest > +dev-db/mariadb-connector-c installed, experienced (NOTE: The default > +MySQL connector in Gentoo Linux is provided by > +dev-db/mysql-connector-c) [Link 1]. This ^ is a very confusing sentence and is way too long. Needs shortening and re-wording, too much commas. > + > +However, downgrades are not supported in MySQL/MariaDB [Link 2]. > + > +In case you already fully upgraded to MariaDB 10.6 (which includes > +executing mysql_upgrade command) and forcefully downgraded your > +MariaDB instance afterwards during the time window when keywords were > +removed, you maybe experiencing different problems: > + > +At best, your forcefully downgraded MariaDB instance prevented startup > +so all you have to do is upgrade to MariaDB 10.6 again to resume > +services. > + > +In case previous MariaDB version was able to start, you are encouraged > +to do a full backup as soon as possible using mysqldump command and > +manually restore each database ("logical downgrade") to prevent any > +data corruption. > + > +Depending on used feature set and from which version you upgraded, > +it is maybe required to do a full restore from a previous backup before > +MariaDB 10.6 upgrade to restore services and prevent any data loss or > +future runtime errors. > + > +In case you are using MariaDB in a cluster and/or Galera setup you > +probably have to rebuild the entire cluster in case the upgrade to > +MariaDB 10.6 was already replicated (using pt-table-checksum from > +dev-db/percona-toolkit can help you to validate your cluster). > + > +Keep in mind that due to the forced downgraded, point-in-time recovery > +may not be available to the extent that you are used to. > + > +Link 1: https://bugs.gentoo.org/825234#c8 > + > +Link 2: > https://mariadb.com/kb/en/downgrading-between-major-versions-of-mariadb/ > -- > 2.34.0 > > -- Best regards, Georgy