Regarding VACUUM, I chose a « manual » approach for now, given the impact it has on Gladys availability on large DBs.
I removed the VACUUM during device registration, and I added a manual button in the system settings with text that clearly states Gladys will be unavailable for a certain time due to VACUUM.
The idea is first to see how long VACUUM takes on different instances, and let the user choose whether to run it or not.
Then, we could possibly add a monthly night-time job, for example, but it should be clearly communicated and made disableable for those who want maximum Gladys availability.
