Customer reported bug that running the command
./console core:purge-old-archive-data all didn't save DB space. They also had to run
./console database:optimize-archive-tables all afterwards.
core:purge-old-archive-dataconsole command, let's remove
--force-optimize-tablesoption and always optimise tables
Db::optimizeTableslet's remove the second parameter
$force = falseand always force optimise tables (the code already checks
isOptimizeInnoDBSupportedwhich should be enough)
On Cloud we don't want to run always optimize. So this would need to be again a setting to disable this behaviour.
Ok, removed the second bullet point, but first one still valid (as per discussion)