[debian-mysql] Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31

[Yves-Alexis Perez]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Sun, 2021-10-24 at 00:51 +0800, Marc Gallet wrote:
> Am I to understand that the expected path forward with what is supposed to be
> a minor update offered on oldstable is that everyone shall dump their databases,
> delete the data folder, restore, then upgrade???
> 
> Sure I can do that, not happy to, but I can.
> 
> However, that's an awful upgrade path and user experience for what would have
> normally been a mere and uneventful "apt-get upgrade". I do hope not everyone
> still on buster will have to do that after learning about it from a bug report.

To be fair, I think we might actually have an issue with our databases and the
way they are stored: it's likely they do have some corruption in it that
doesn't show before 10.3.31 but doesn't mean they're ok. So all in all even if
the bug is fixed, it might be a good idea to do that backup/restore dance.
> 
> Seems to me it would be better to not have pushed this update to oldstable in
> the first place. (I'm not familiar with process, but could it be possibly undone,
> such that users stay on 10.3.29 and are not proposed the broken upgrade?).

Well, 10.3.31 actually fixes security issues so you don't really want to stay behind in any case.

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmF1SFUACgkQ3rYcyPpX
RFtQjgf/ckSNysleNW7oW6QWOrlJrG5DKxw9LhhJYD/0zIMlDUKL3YSJM7VqCUS+
EFrUB2N/r7/p1d7/aispWKWuk3O6LvYmkoqv3V/GddverxZwfsaCCOnBkJXeEWgv
dNKw2rv4Vt1xbhFtcISWnxNA3ES48cM1Vfdt7tUL7Qn21RreLYMNvtzez6d9f8mC
p1Oan7JHQyPj9Ad50DR0IrnIAc+YAz1RaqQ9Dc98wfW5CkUXqLMk6kXWNImUYNiW
zxEtuzDN8jAD1gOAwKLrfKNAIFLwdS0dO0aM6q/ILwSWwgHBdlTn8wkOXgZ8NsEI
2Jlw4arlq2dpPJGjfu912CuLtmmGRw==
=PtQ4
-----END PGP SIGNATURE-----