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

[Yves-Alexis Perez]

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

On Fri, 2021-10-22 at 02:13 +0800, Marc Gallet wrote:
> 
> Am I correct to assume this issue is still relevant for buster and that
> for now, I should simply defer the upgrade (marking the packages to be
> held back) and simply wait for this bug to be resolved?

Hi Marc,

as far as I can tell, yes the bug is still present. The fix attempt didn't
work for me, maybe because my database is already corrupted, or maybe because
it's actually not fixed at all.

I have yet to try to dump my database under 10.3.25 and import it under
10.3.31 to check if it fixes the issue.

Another possibility would be to rebuild with
e46f76c9749d7758765ba274a212cfc2dcf3eeb8 (which Ondrej identified as the first
bad commit) reverted.

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmFynPYACgkQ3rYcyPpX
RFvOoAgAwWYdiSdkN/Wau7jUf68hUVgcy6hIp1Wo5IbKIZcizs0KyEguOA6gjff2
Zv7VnTJ3Fv+y3i98FgV2f2rYbLkNw+PDmrdWjyYIzXIDS7jb05CZ1CwaAb0ni/qm
rkYKm2vQIPl9sajvgWhbXkVgMcFDP9E25tELjHb3SX3YhhoTKQliTD+JUbSEr5Pw
6N16Z9mUFHuNYhDw99OUKbWxhJpAPa/VYu5ZzqR5gfYjYUQrQ3VXWxlJKsfhCBv+
+a3+GFR2pHVGWB6JUPzWj0wdwq5D2zp04uP1ZLtL40PrqwpH2Wd8rWIHbTHMszVY
MjWAgfmlJnaU/eqIjtSqVVjDPIm+Jg==
=91rF
-----END PGP SIGNATURE-----