Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'v got a 220M db running under PgSQL 8.1 (upgrade not possible ATM.). If I do a reindex, the db size goes to 220 but then it starts growing over time (it shoudln't), a few megs per day.

I did progressively increase the autovacuum (enabled) daemon running frequence to reach finally those settings:

autovacuum = on
autovacuum_naptime = 25
autovacuum_vacuum_threshold = 40
autovacuum_analyze_threshold = 30
autovacuum_vacuum_scale_factor = 0.1
autovacuum_analyze_scale_factor = 0.05

This is even more than the recommended settings (default on a 8.4) but still, the database is growing.

And regarding the FSM (VACUUM VERBOSE output): INFO: free space map contains 2081 pages in 76 relations DETAIL: A total of 3088 page slots are in use (including overhead). 3088 page slots are required to track all free space. Current limits are: 20000 page slots, 1000 relations, using 222 KB.

So, I really don't know what should I do next in order to solve this database growing issue (beside upgrading), any though?

share|improve this question
Are you sure this is not because you are simply writing data to the database? –  bart613 Sep 5 '11 at 14:42
It shouldn't growth, do you know how I can check the size of each table to see if everything looks normal? –  Henry-Nicolas Tourneur Sep 5 '11 at 14:52
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.