• How to verify a clean MariaDB shutdown in logs before a major version u

    From =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?@21:1/5 to All on Thu Jun 19 14:10:01 2025
    Hi!

    Congrats on the MariaDB 11.8 release! So far in Debian and Ubuntu no regressions have been reported and looks everything is working well.

    The most frequent thing I see people complain about is not new to
    11.8, but I think introduced in 10.4 with InnoDB refusing to start if
    crash recovery is needed for a database of an earlier major version.

    This is explained in e.g. https://web.archive.org/web/20240912062010/https://mariadb.com/kb/en/innodb-upgrade-after-a-crash-is-not-supported/

    To help DBAs ensure they have a clean shutdown before doing a major
    version upgrade, I was wondering what are the best ways to confirm a
    clean shutdown by checking the MariaDB logs or files in
    /var/log/mysql? Specifically, what log entries or patterns in the
    MariaDB logs indicate a clean shutdown?

    Additionally, are there particular files or indicators in
    /var/log/mysql that reliably show the clean shutdown status? For
    example, if all buffers were flushed, should I expect that some files
    have size zero?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)