Our current mount point for our main db is saturated (the one for the worker and currently for the archiver in its main design).
But, as it turns out, we have softwareheritage-log db which is around 1.1Tb (this is one quarter of the available space for the main cluster).
So we can:
- clean up a bit (by removing logs with log level > info older than 1 month).
- dump the db softwareheritage-log
- restore that dump in the other cluster (the other mount point which is standard hdd with much space).
-> The db will be compressed to what's needed only so less than 1.1Tb this time.
- drop softwareheritage-log in the main cluster
- Update /etc/pbbouncer/pgbouncer.ini with the new db port to keep serving softwareheritage-log
- As we use pgbouncer, this should not change anything downstream.