Topic: InnoDB database size reduction after MySQL upgrade?

I was on MySQL v5.5.28-3 and my InnoDB database was 3.09GB in size.
After upgrading to v5.5.29 it went down in size to 2.55GB

Database backups with "mydumper" confirm this aswell: 3.35GB vs 2.95GB
But after compression into tar.bz2 archive there was no difference, 606MB before & after...
Does the installation script run the "mysql_upgrade" binary or what could account for this reduction in size?

Re: InnoDB database size reduction after MySQL upgrade?

There is no action in the installation script (except the service restart).
Mostly because most actions (mysql_upgrade or ...) will requires the root password.

Check if there is explanation in the mysql.log (first restart after update)

AFAIK, there is a lot of InnoDB bug fixed in this version, perhaps this is related.

Laptop:  Fedora 38 + rpmfusion + remi (SCL only)
x86_64 builder: Fedora 39 + rpmfusion + remi-test
aarch64 builder: RHEL 9 with EPEL
Hosting Server: CentOS 8 Stream with EPEL, rpmfusion, remi

Re: InnoDB database size reduction after MySQL upgrade?

There is nothing out of the ordinary in the logs from the upgrade, all went well...
We did have an issue where we ran out of disk space a couple months earlier, but the server had been rebooted anyway since then so I don't think that should be it either.

"InnoDB: If a CREATE TABLE statement failed due to a disk full error, some memory allocated during the operation was not freed properly. (Bug #14708715)"