[framework] VACUUM FULL ANALYZE is now run once a week

[vitek-rostislav]

Q	A
Description, reason for the PR	It is a good practice to garbage-collect the Postgres database once in a while in production to avoid performance issues. We added a CRON module that performs VACUUM FULL ANALYZE on the database once a week so we don't have to think about it and run it manually anymore.
New feature	Yes
BC breaks	No
Fixes issues	...
Have you read and signed our License Agreement for contributions?	Yes

---

🌐 Live Preview:

• https://rv-vacuum.odin.shopsys.cloud
• https://cz.rv-vacuum.odin.shopsys.cloud

[henzigo]

Those functions are just duplicated in our base:

waitUntilOtherCronModulesOff() -> CronWatchCommand
lockAllCronModules() -> CronLockCommand
maintenanceOn() and maintenanceOff() -> MaintenanceModeCommand

[henzigo]

I don't like the idea of making VACUUM FULL from the application. Additionally, you should run VACUUM FULL as an edge case and not regularly.

Postgres has AUTOVACUUM that should handle bloat in databases. If you have miswritten your application then you have to use VACUUM FULL. Running it periodically covers problems in your application.

Another view can be that ANALYSE rebuilds all statistics instead of updating them. So this means that this command can negatively impact the performance of some SQL commands.

I don't say we should entirely avoid using VACUUM FULL, but we should do that manually as an edge case.

There is an outdated but still relevant article about it: https://wiki.postgresql.org/wiki/VACUUM_FULL