action #100979
open
configure better auto-vacuum for our database(s)
Added by okurz over 2 years ago.
Updated over 2 years ago.
Description
Motivation¶
Over 80% space of /srv on OSD are used up. In #100859 we already identified that it's mostly our database and a re-import is much smaller so maybe better auto-vacuum helps.
Acceptance Criteria¶
AC1: auto-vacuum is conducted on a useful period for OSD
Suggestions¶
Related issues
1 (1 open — 0 closed)
- Copied from action #100976: specific alert about the size of our database, maybe even database tables? added
postgresql is doing a vacuum itself once 20% of the rows changed. you could tweak this parameter, but postgresql won't shrink the table - only make deleted rows reaccessible.
The manual vacuuming @coolo and me did as part of #100859 helped freeing disk space. As @coolo mentioned, the automatic vacuuming won't free disk space (as it doesn't free space on filesystem level).
Not sure whether we want to automate the "full" vacuuming (VACUUM FULL …) we did manually because while it is running the database is basically not usable and it is also not recommended by upstream.
Tweaking the threshold for the auto-vacuuming might be sufficient. It won't free disk space but could help us to not use that much disk space in the first place (as deleted rows are earlier reused instead).
Also available in: Atom
PDF