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

[Yves-Alexis Perez]

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

On Thu, 2021-10-14 at 19:38 +0200, Ondrej Zary wrote:
>     MDEV-15912: Remove traces of insert_undo
> 
>     Let us simply refuse an upgrade from earlier versions if the
>     upgrade procedure was not followed. This simplifies the purge,
>     commit, and rollback of transactions.
> 
>     Before upgrading to MariaDB 10.3 or later, a clean shutdown
>     of the server (with innodb_fast_shutdown=1 or 0) is necessary,
>     to ensure that any incomplete transactions are rolled back.
>     The undo log format was changed in MDEV-12288. There is only
>     one persistent undo log for each transaction.


Hi Ondrej,
it might be worth trying with that patch reverted, but I'm a bit confused at
the commit message. That seems to imply my server didn't have a clean shutdown
before upgrading to 10.3, which is possible but that upgrade is quite old by
now (afaict it's between Stretch and Buster), so I'm unsure what to do now.

innodb_fast_shutdown=0 doesn't terminate on 10.3.25, and I'm not sure if there
are other ways to ensure a “clean shutdown”.

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

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmFynjAACgkQ3rYcyPpX
RFtw9Qf/WcV91Ea5ltjqC4rzuNn877t0sjbdYx/4gESfevP+OY8lBboAckXQfejK
FAMZIrRtQ6vmLiTDpYEZgBEqVuyPICFJ2kuK6ejxzYT3zpUqoXMTi21fUd2pivKF
IVVHdMlFEgHfErGxN66Rv8m/OZUknfDAmkdAgKO0+WS+HuD/wuN7Y2zRCQBZ5PJg
8GJUZK+9O/7UdfHtxJvEja4U7B8G+bwQhKBNtgolOIrfapakB9b63KasJ18PVpQm
TpkL8XdolAG/cvqxp6UYjVdatOTmceH/tME0xzbnad/hNxzR4MZKjUlCrZ8T0zgW
WvXUZt1YsEivScpY15T32FELKPQeDQ==
=92/m
-----END PGP SIGNATURE-----