During larger registration campaigns postgresql fills a LOT of disk space
- vhr21 database volume size now (retrieved via
docker system df -v
) 337.1GB
Relevant tables sizes via d+\ in dbshell:
public | coverages_bandstatistics | table | vhr21_user | permanent | 302 MB
public | coverages_eoobject | table | vhr21_user | permanent | 313 GB
The growth does not seem to be linear
- on staging I registered 20k products and the database size increased by 18GB
- on production, I registered different 55k products and the database size is **313GB **
Confirmed that coverages do not have footprint and the product footprints have been correctly simplified.
Vacuuming the database without the -f
flag does not restore any space and takes hours.
Vacuuming afterwards and adding the -f
flag takes a few minutes and cuts down the used space to expected values:
vhr21-pdas_db-data 2 1.659GB
public | coverages_eoobject | table | vhr21_user | permanent | 99 MB