Hi Thicham,

I had a similar issue some months ago. The problem was located in an module that stored big binary files in the database.

I would suggest that you analyse your database to find out you which tables store a big amount of data. To do this, you can run follow query on you database:

SELECT nspname || '.' || relname AS "relation",    pg_size_pretty(pg_total_relation_size(C.oid)) AS "total_size"  FROM pg_class C  LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace)  WHERE nspname NOT IN ('pg_catalog', 'information_schema')    AND C.relkind <> 'i'    AND nspname !~ '^pg_toast'  ORDER BY pg_total_relation_size(C.oid) DESC  LIMIT 20;

The result of this query will show the name of the table and its disk usage for the 20 biggest tables. Once you know which tables are growing very fast you can focus the analysis on the corresponding module.

You can find useful information about disk usage under: https://wiki.postgresql.org/wiki/Disk_Usage

Best regards

Yvan